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
Use un-existing properties on the theme object OR At the end of your file just type any random string
Save the file
Kaboom
Current behavior
Crashes the dev server and it needs to restart
Expected behavior
Log error or show the Error dialog in browser.
Context
When we try to access properties on undefined the wyw-in-js transformation crashes and leaves nextjs in a hanging state. Only way to recover from it is to fix the error and restart the dev-server.
What is happening is that the parsing of the css crashes. It looks like we just assumes that the key exists and never handle that wyw-in-js throws an error here.
Wrapping build in a try catch solves it. But not sure that this is the place we should fix it.
Also found another related issues while i accidentally smashed my keyboard and saved my component. It just crashes and never recovers from the crashed state. Look here for an example.
Steps to reproduce
Current behavior
Crashes the dev server and it needs to restart
Expected behavior
Log error or show the Error dialog in browser.
Context
When we try to access properties on undefined the wyw-in-js transformation crashes and leaves nextjs in a hanging state. Only way to recover from it is to fix the error and restart the dev-server.
What is happening is that the parsing of the css crashes. It looks like we just assumes that the key exists and never handle that wyw-in-js throws an error here.
Wrapping build in a try catch solves it. But not sure that this is the place we should fix it.
See here for a working example.
Also found another related issues while i accidentally smashed my keyboard and saved my component. It just crashes and never recovers from the crashed state. Look here for an example.
Your environment
npx @mui/envinfo
Search keywords: wyw-in-js, css
The text was updated successfully, but these errors were encountered: