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

discussion: Import maps should be an unstable feature #4931

Closed
lucacasonato opened this issue Apr 27, 2020 · 2 comments · Fixed by #4934
Closed

discussion: Import maps should be an unstable feature #4931

lucacasonato opened this issue Apr 27, 2020 · 2 comments · Fixed by #4934

Comments

@lucacasonato
Copy link
Member

Deno is currently the only runtime that implements import maps. They are not supported by any browser at the moment.

  • Chrome: did an origin trial from M74 to M76, ending September 4th 2019. No action since then. Currently not scheduled for an upcoming release.
  • Firefox: position unclear (Import maps mozilla/standards-positions#146). Not implemented or experimented.
  • Safari: No signals. Not implemented. No tracking issue.
  • Node: No signals. Not implemented. No tracking issue.

We are taking quite the risk by implementing this spec and supporting it in stable before it becomes a w3c standard and is implemented by other runtimes. I think we should move the entire import map feature under the --unstable flag.

cc @ry @bartlomieju


Ref WICG/import-maps#212

@ry
Copy link
Member

ry commented Apr 27, 2020

Yes I’m all for it. We should make it fail without also specifying —unstable flag. Can be implemented using State::check_unstable()

@lucacasonato
Copy link
Member Author

I'm on it.

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

Successfully merging a pull request may close this issue.

2 participants