import.meta.resolve second argument

[guybedford]

Chrome is now moving towards shipping import.meta.resolve as discussed in #7296.

The current form takes a single argument to resolve.

Node.js implements the ability to pass an optional second argument to import.meta.resolve for a custom parentURL to resolve against, allowing import.meta.resolve to act as a generic resolver in various contexts, which may be useful as a generic way to expose the global resolver.

I wanted to post this as a tracking bug for Deno to implement this along with #7296. Further discussion welcome.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.