We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
access to svelte/internal should be limited to blessed code (mostly compiler output). But for technical reasons it is exported from the svelte package and can be imported by anyone, and a lot of code does: https://github.com/search?q=%22svelte%2Finternal%22+&type=code
add a guard in resolveId that logs a warning or throws an error upon encountering such an import.
maybe eslint-plugin-svelte would also be able to flag these
nice to have
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the problem
access to svelte/internal should be limited to blessed code (mostly compiler output).
But for technical reasons it is exported from the svelte package and can be imported by anyone, and a lot of code does: https://github.com/search?q=%22svelte%2Finternal%22+&type=code
Describe the proposed solution
add a guard in resolveId that logs a warning or throws an error upon encountering such an import.
Alternatives considered
maybe eslint-plugin-svelte would also be able to flag these
Importance
nice to have
The text was updated successfully, but these errors were encountered: