-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Cleanup prebundleSvelteLibraries #222
Comments
Update: no2 and no3 are being dealt at vitejs/vite#6801 |
Short question: what will be the default behavior after this is finished? Will that be Background: I'm creating a sveltekit library (see here), but in order to be able to use it right now, every client has to configure |
Hi. Ideally this will be the new default behaviour, but I would put it in a short experimental phase first just in case there are edge cases.
This should be handled by default by |
Awesome! Good to know that this is supposed to "just" work. I'll double check whether I'm using all the latest versions of svelte/kit/vite and verify whether UPDATE: managed to get it working 🎉 . There where only two troublesome dependencies left, I could replace one and create a workaround for the other. |
Describe the problem
Fix the remaining issues for
prebundleSvelteLibraries
, which should be the correct way forward for Vite prebundling of Svelte libraries. Namely:Some fixes may need to be in Vite core. Collecting these issue here so I don't forget, or if someone likes to tackle them.
Describe the proposed solution
Goal is to fix them by year end.
Alternatives considered
Not fix them by year end
Importance
would make my life easier
The text was updated successfully, but these errors were encountered: