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

Question: how does this spec become official? #217

Closed
andykais opened this issue May 21, 2020 · 5 comments
Closed

Question: how does this spec become official? #217

andykais opened this issue May 21, 2020 · 5 comments

Comments

@andykais
Copy link

Hi, I think this is a great idea, and its nice to see deno already pick up import-maps, but what about browsers and node? How do they adopt this pattern as well? Does this spec have a place in the tc39 proposals?

@domenic
Copy link
Collaborator

domenic commented May 21, 2020

I think what you're asking is, how do you get implementers to implement the spec? For that, the process varies by implementer.

For Chromium, we're looking to ship this soon; we have it behind a flag, but were delayed in launching it due to COVID shifting some resources around.

For Gecko, their discussion is happening at mozilla/standards-positions#146.

For Node, I'm aware of a discussion at nodejs/node#49443.

I haven't heard anything from WebKit.

@andykais
Copy link
Author

Thank you for the info! I assume typescript will follow behind node as well?

@joeldenning
Copy link
Contributor

Deno has already shipped import maps, under an experimental flag. Documentation at https://deno.land/manual/linking_to_external_code/import_maps

@domenic
Copy link
Collaborator

domenic commented May 21, 2020

I assume typescript will follow behind node as well?

I'm not sure. I was hoping you'd pick up on the pattern of my post, which is, that each individual implementer has their own plans, and you need to ask them individually :).

@andykais
Copy link
Author

Got it, I will look into that and see if an issue needs to be created. It could be handy to have an issue tracking the progress in each implementer so devs know where to direct their support in the future. My question is answers though so I will close this issue. Thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants