-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Svelte 5: Can we have strict mode? #9416
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
Comments
Only |
+1 for reporting Maybe change the wording of
into a stronger stance . |
Moving this to the 5.0 milestone — agree that warning on |
- warn on slots and event handlers in runes mode - error on `<slot>` + `{@render ...}` tag usage in same component closes #9416
* breaking: warn/error on old syntax in runes mode - warn on slots and event handlers in runes mode - error on `<slot>` + `{@render ...}` tag usage in same component closes #9416 * render tag + slot could occur in legacy mode as well, error there, too
Uh oh!
There was an error while loading. Please reload this page.
Describe the problem
When testing svelte 5, I want to get warnings (or errors) when using the svelte features that have been superseded in Svelte 5, ie:
I respect (and need!) backwards compatibility, but I love the small surface-area of Svelte. With Svelte 5 I'm not thrilled at the idea of different team-members adopting different approaches. it sounds... complex
Describe the proposed solution
Have a flag in our config files, AND on the documentation
Alternatives considered
Swallow sadness
Importance
would make my life easier
The text was updated successfully, but these errors were encountered: