-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
esm: add a runtime warning when using import assertions #46901
esm: add a runtime warning when using import assertions #46901
Conversation
Review requested:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should wait for a response from tc39/proposal-import-attributes#127 (comment) before landing this.
'Import assertions are not a stable feature of the JavaScript language, ' + | ||
'avoid relying on their current behavior and syntax as those might change ' + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comma splice.
'Import assertions are not a stable feature of the JavaScript language, ' + | |
'avoid relying on their current behavior and syntax as those might change ' + | |
'Import assertions are not a stable feature of the JavaScript language. ' + | |
'Avoid relying on their current behavior and syntax as those might change ' + |
It wouldn't be possible for TC39 to provide any timing guarantees - the proposal champions may be able to promise they're ready to present in March, but nobody can predict consensus ahead of time. Multiple delegates have expressed that "assert" syntax is inappropriate for something that's not an assertion anymore, and the web can't use the assertion semantics, so the semantics will change - which suggests to me that the syntax is likely to as well, regardless of whether Chrome decides to unship the current syntax or not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Landed in 5a7491b |
@aduh95 This landed without #46901 (comment) being addressed? The current text is incorrect grammar. |
Refs: #46901 (comment) PR-URL: #46971 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #46901 (comment) PR-URL: #46971 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #46901 (comment) PR-URL: #46971 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #46901 (comment) PR-URL: #46971 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Jacob Smith <jacob@frende.me> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #46830
/cc @nodejs/loaders