Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

import.meta.resolve() #647

Closed
domenic opened this issue Jun 6, 2022 · 3 comments
Closed

import.meta.resolve() #647

domenic opened this issue Jun 6, 2022 · 3 comments

Comments

@domenic
Copy link
Contributor

domenic commented Jun 6, 2022

Request for Mozilla Position on an Emerging Web Specification

Other information

This has unofficial supportive comments from @annevk and @codehag in the pull request, but I thought it'd be best to get an official position as well.

This will be useful to test import maps, which are "worth prototyping".

@annevk
Copy link
Contributor

annevk commented Jun 7, 2022

Asked a clarifying question in whatwg/html#5572 (comment) as I'd really like for APIs like this to be widely adopted.

@codehag
Copy link
Collaborator

codehag commented Jun 15, 2022

From my perspective, this is worth prototyping in line with import maps, as it is a requirement for adequately testing that spec. In addition, I think that this provides a useful utility for inspecting the resolution of a specifier or relative URL, especially in the context of import maps.

@bgrins
Copy link
Member

bgrins commented Jun 16, 2022

Thanks Yulia! I'm going to label as worth prototyping and close the issue as opposed to asking you to do a PR, since this looks like a logical addition to import maps (which we alread have a stated position for). But if you think it should be documented more formally please feel free to send one over.

@bgrins bgrins closed this as completed Jun 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants