-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Compiler options runes: true
should only affects the user components as defined in src
#11523
Comments
You can just install svelte 5 and start using runes in your components to unlock runes mode for those components. |
I don't think the behavior here should change, nor should the core compiler be aware of things like 'in The recommended way to handle this would be with https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/config.md#dynamiccompileoptions - although the code example is out of date - it no longer lives under |
I didn't know about this config entry, I'll make sure to check it out! Thanks for your fast answer! |
#10359 (comment) - I have used a similar approach in SvelteKit exactly with |
Describe the bug
Currently (at least, until 5.0.0-next.125), when we set
runes: true
inside ofsvelte.config.js
, all the components inside our app (including the ones packaged from external libraries) are forced into runes mode.However this has the side effect of preventing the use of slighly older libraries that might not have native runes support, one such example is
sveltekit-superforms
.My question is should the compiler options
runes: trues
only affects user components as defined insrc
? If not, the docs should clearly state that it also affects the third party ones.See the reproduction link bellow for an example.
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-tqyv6t
Logs
No response
System Info
System: OS: Linux 5.0 undefined CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz Memory: 0 Bytes / 0 Bytes Shell: 1.0 - /bin/jsh Binaries: Node: 18.18.0 - /usr/local/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 10.2.3 - /usr/local/bin/npm pnpm: 8.15.6 - /usr/local/bin/pnpm npmPackages: svelte: ^5.0.0-next.125 => 5.0.0-next.125
Severity
blocking an upgrade
The text was updated successfully, but these errors were encountered: