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
Describe the bug
Currently, <style src="doesnt/exist.scss"></style> will compile into <style src="doesnt/exist.scss">undefined</style>, which crashes the Svelte style parser. It would be nice to handle such situations by simply creating an empty style tag, emitting an error message in the console, that way at least the server runs.
in src/App.svelte, remove the content of the <style> tag and add src="doesnt/exist.scss"
run the development server
Expected behavior
The server should run without crashing, warning the developer about the error.
Additional context
Not sure if the same problem persists with other style processors and other script or markup processors, for that matter. Also not sure if this is intended behaviour.
The reason for this request is that in some cases, crashing a server makes Rollup lose track of dependencies, not rebuilding even after one fixes the faulty path
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Currently,
<style src="doesnt/exist.scss"></style>
will compile into<style src="doesnt/exist.scss">undefined</style>
, which crashes the Svelte style parser. It would be nice to handle such situations by simply creating an empty style tag, emitting an error message in the console, that way at least the server runs.To Reproduce
svelte-preprocess
andnode-sass
autoPreprocess
torollup.config.js
src/App.svelte
, remove the content of the<style>
tag and addsrc="doesnt/exist.scss"
Expected behavior
The server should run without crashing, warning the developer about the error.
Additional context
Not sure if the same problem persists with other style processors and other script or markup processors, for that matter. Also not sure if this is intended behaviour.
The reason for this request is that in some cases, crashing a server makes Rollup lose track of dependencies, not rebuilding even after one fixes the faulty path
The text was updated successfully, but these errors were encountered: