Skip to content

Issues: tc39/proposal-import-attributes

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.

Sign up for GitHub

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

32 Open 55 Closed
32 Open 55 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Support gating with Progressive Enhancement or Graceful Degredation
#153 opened Mar 6, 2024 by Westbrook
4
Restrict generalization by scoping private keys
#147 opened Sep 25, 2023 by Ayc0
2
There should be an escape hatch to allow unknown import attributes
#132 opened Mar 14, 2023 by gibson042
3
Broken references in import assertions
#128 opened Feb 2, 2023 by dontcallmedom-bot
1 task
Examples?
#122 opened May 5, 2022 by ArtemFrontendACTUM
2
Forward compatibility of ignoring unknown keys in the import(…) options bag
#121 opened Apr 7, 2022 by fstirlitz
1
Add type: "any"
#116 opened Nov 11, 2021 by weswigham
12
Suggestion: only one valid type per resolved URL
#114 opened Oct 19, 2021 by GeoffreyBooth
8
Could the static and dynamic import syntaxes be more symmetric?
#99 opened Sep 22, 2020 by devongovett
14
Why not indicate that a module is non-executable with a simpler or shorthand syntax?
#90 opened Aug 1, 2020 by CxRes
2
Consider strengthening host invariants proposed resolution: no action to take
#64 opened May 28, 2020 by littledan
8
Unmixing type from other attributes
#63 opened May 27, 2020 by eemeli
18
Privilege of a type
#60 opened May 22, 2020 by annevk
1
Should we allow more than just strings as module attributes? proposed resolution: follow-on proposal
#59 opened May 20, 2020 by littledan
1
Multi-typed modules follow-on proposal
#56 opened May 13, 2020 by bmeck
21
Dynamic import should accept multiple arguments proposed resolution: no action to take
#55 opened May 12, 2020 by Jack-Works
8
Should type: "js" work?
#49 opened Mar 26, 2020 by dandclark
12
Potential use case: mocking internals discussion
#46 opened Mar 18, 2020 by MylesBorins
7
Type of builtin modules proposed resolution: follow-on proposal proposed resolution: no action to take
#35 opened Dec 17, 2019 by bmeck
20
Attributes divergence proposed resolution: hosts to decide
#34 opened Dec 9, 2019 by xtuc
3
Semantics of unrecognized types proposed resolution: hosts to decide
#27 opened Nov 9, 2019 by littledan
37
Semantics of this feature in Node.js proposed resolution: hosts to decide
#25 opened Nov 9, 2019 by littledan
20
Semantics of this feature in HTML/the Web proposed resolution: hosts to decide
#24 opened Nov 9, 2019 by littledan stage 3
15
How should this interact with tools? proposed resolution: hosts to decide
#22 opened Nov 8, 2019 by littledan
4
How should unrecognized attributes or types be handled? proposed resolution: hosts to decide
#21 opened Nov 8, 2019 by littledan
15
ProTip! Add no:assignee to see everything that’s not assigned.