Skip to content

Conversation

@connorjclark
Copy link
Collaborator

These won't be acted on. ref #12689

@connorjclark connorjclark requested a review from a team as a code owner September 2, 2022 22:25
@connorjclark connorjclark requested review from adamraine and removed request for a team September 2, 2022 22:25
}), function(err) {
// We're expecting not to find parent class Audit, so only reject on our
// own custom locate audit error, not the usual MODULE_NOT_FOUND.
// TODO(esmodules): Test migration note:
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was already fixed actually

'It\'s possible a Chrome extension or other eval\'d code is the source.';

// TODO(esmodules): don't use default export
export default URLShim;
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should be a named export and used as URLShim everywhere (to denote it isn't the global node URL)? atm we just kinda shadow the global value in all the imports. so not 100% sure about ignoring this TODO.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If not 100% sure we could just leave it as a normal TODO but then we will probably never get to it 🤷

Copy link
Collaborator Author

@connorjclark connorjclark Sep 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#14182 accidentally deleted the comment here about "remove this (from the build shimming) eventually". should be fine to remove now, and then make URLShim be called literally anything else. Could we maybe even remove the extending from URL and rename the things url-utils (and export its methods)?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

@connorjclark connorjclark Sep 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could also just keep export const URL = globalThis.URL; as its pretty minimal... and there could be dependencies using url that are out of our control. anyway, this is a separate thing.

'It\'s possible a Chrome extension or other eval\'d code is the source.';

// TODO(esmodules): don't use default export
export default URLShim;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If not 100% sure we could just leave it as a normal TODO but then we will probably never get to it 🤷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants