You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TransactionType is an enum and all it's properties have this warning when used inside $: (we haven't started migration to Svelte 5 runes yet.
Properties of objects and arrays are not reactive unless in runes mode. Changes to this property will not cause the reactive statement to updatesvelte(reactive_declaration_non_reactive_property)
Then ran:
pnpm exec eslint .
What did you expect to happen?
I was expecting this to not be an error and instead a warning.
What actually happened?
/src/routes/app/create-envelope-transaction/+page.svelte
16:7 error Properties of objects and arrays are not reactive unless in runes mode. Changes to this property will not cause the reactive statement to update(reactive_declaration_non_reactive_property) svelte/valid-compile
17:11 error Properties of objects and arrays are not reactive unless in runes mode. Changes to this property will not cause the reactive statement to update(reactive_declaration_non_reactive_property) svelte/valid-compile
18:11 error Properties of objects and arrays are not reactive unless in runes mode. Changes to this property will not cause the reactive statement to update(reactive_declaration_non_reactive_property) svelte/valid-compile
Link to GitHub Repo with Minimal Reproducible Example
When I try to ignore it with the following it persists, which makes sense since these are two different tools (one is the Svelte VSCode extension and the other ESLint):
After thoroughly testing I seem to have found that the error steamed from an bogus node_modules (deleting and installing again seems to have fixed the issue). I'm closing this as I'm not able to reproduce in the MRE.
I was thinking about this the wrong way. It's not related to node_modules, it just a different behavior between pnpm check and pnpm eslint .. The first one throws warnings as expected but pnpm eslint . throws the errors which is the unexpected part. The reason I was confused is that we have a custom formatter and it was using pnpm eslint . under the hood instead of directly pnpm check.
Before You File a Bug Report Please Confirm You Have Done The Following...
What version of ESLint are you using?
9.13.0
What version of
eslint-plugin-svelte
are you using?2.46.0
What did you do?
Configuration
TransactionType
is an enum and all it's properties have this warning when used inside$:
(we haven't started migration to Svelte 5 runes yet.Then ran:
What did you expect to happen?
I was expecting this to not be an error and instead a warning.
What actually happened?
Link to GitHub Repo with Minimal Reproducible Example
https://github.com/fev4/reactive-non-reactive
Additional comments
When I try to ignore it with the following it persists, which makes sense since these are two different tools (one is the Svelte VSCode extension and the other ESLint):
The text was updated successfully, but these errors were encountered: