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
Describe the feature
Currently vite only knows that .svelte is transformed to js but svelte can be used with other extensions aswell (eg .svx , .svg )
.svelte
.svx
.svg
A Usecase Resolve the current situation where non ".svelte" svelte components require ?import to be imported correctly
Alternatives Check out if the import marker could be added during resolveId?
Additional context ?import marker added in sveltekit: https://github.com/sveltejs/kit/blob/1c78dec3b65d407db70a555ff54cc11442dcdc07/packages/kit/src/core/dev/index.js#L254
initial PR on vite (needs to be rebased) vitejs/vite#3219
new PR on vite vitejs/vite#3828
The text was updated successfully, but these errors were encountered:
unfortunately vitejs/vite#3828 has been set to Draft and it is unclear how vite is handling this in the future. So for now we wait...
Sorry, something went wrong.
chore: remove vite config option knownJsSrcExtensions as vite won't s…
76ed865
…upport it in the near future [skip ci] (#85) see #60
No branches or pull requests
Describe the feature
Currently vite only knows that
.svelte
is transformed to js but svelte can be used with other extensions aswell (eg.svx
,.svg
)A Usecase
Resolve the current situation where non ".svelte" svelte components require ?import to be imported correctly
Alternatives
Check out if the import marker could be added during resolveId?
Additional context
?import marker added in sveltekit: https://github.com/sveltejs/kit/blob/1c78dec3b65d407db70a555ff54cc11442dcdc07/packages/kit/src/core/dev/index.js#L254
initial PR on vite (needs to be rebased)
vitejs/vite#3219
new PR on vite
vitejs/vite#3828
The text was updated successfully, but these errors were encountered: