We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Mentioned in the Appendix:
It could also be possible to use specialized tokens in place of Identifier prefix, for example similar to C/C++:
import { ... } from <SomeStandardModule>;
Static analysis tools (like webpack, bundlers, lint, etc.) will need to be able to identify if a module specifier is a built-in module, or not.
Therefore, an enforceable, and differentiating sigil/keyword/symbol/syntax would be heavily preferred.
I personally think the above example would be perfect! As a parser could distinguish a module using a built-in module on a single pass.
The text was updated successfully, but these errors were encountered:
I can delve into the webpack specific scenario here if it is not clear.
Sorry, something went wrong.
No branches or pull requests
Mentioned in the Appendix:
Static analysis tools (like webpack, bundlers, lint, etc.) will need to be able to identify if a module specifier is a built-in module, or not.
Therefore, an enforceable, and differentiating sigil/keyword/symbol/syntax would be heavily preferred.
I personally think the above example would be perfect! As a parser could distinguish a module using a built-in module on a single pass.
The text was updated successfully, but these errors were encountered: