Add possibility to silence module-script-reactive-declaration warning

[dummdidumm]

Is your feature request related to a problem? Please describe.
In #5847 I expressed the concern that people might want to use module variables inside reactive statements, knowing that reactivity will not be triggered on changes to them. This means it should be possible to silence the warning.

Describe the solution you'd like
<!-- svelte-ignore module-script-reactive-declaration --> at the top of the component or // svelte-ignore module-script-reactive-declaration should silence the warning

How important is this feature to you?
Nice to have to not have this warning make unnecessary noise

Workaround in the meantime
You can globally silence this. For svelte-check, do --compiler-warnings "module-script-reactive-declaration:ignore". A similar option is available for the VS Code extension.

[ribizli]

IMHO, just don't warn on const would be really helpful.

[lights0123]

And functions too

[natemartinsf]

Agree. I'm exporting a const to use the value in other modules, and that's causing this warning too. I suppose workarounds are to make this a readable store (which seems a lot heavier than just exporting a const), or creating a constants.js file that gets imported in multiple places.

[j3rem1e]

I don't see the point of this warning. A warning should be emitted if the code can be improved or if something is wrong.
Here, there is nothing to do but stop using scripts module.

This warning sounds like "read the doc".

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dummdidumm]

Still relevant

[Conduitry]

This has been released in 3.39.0.