Dev mode is currently broken
See original GitHub issueThe npm run dev
is currently broken leading to a lot of 4xx and 5xx errors since the dev mode implementation is half baked. The production mode runs just fine with npm run build
followed by a npm run start
. HMR isn’t supported in production mode, so any changes to React side of things need a npm run build
and refresh in the embedded app to update.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Xbox One Dev Mode is broken after it was last updated. Apps ...
Xbox One Dev Mode is broken after it was last updated. Apps installed within it will fail to run after a reboot. Needs...
Read more >[UPDATED] Microsoft Is (no longer) disabling Dev Mode ...
UPDATE: Microsoft says it has no plans to remove or disable dev mode on Xbox consoles. A number of Partner Center accounts were...
Read more >Dev-mode broken · Issue #6523 · jupyterlab ... - GitHub
Describe the bug For the current master adf2f3f, the dev mode is broken. Nota: compiling and running in standard mode (i.e. through jupyter ......
Read more >Dev mode broken?, page 1 - Forum - GOG.com
I managed to somehow stick myself in a wall, and wanted to use Dev/Producer Mode to get out. However, while I can enable...
Read more >Fix Developer Mode in Windows 10 Build 17672 - Winaero
The Developer Mode feature is broken in recently released Windows 10 Build 17672. Here's a quick workaround to resolve the issue.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After reading some documentation,
npm run dev
is now working again. Also thanks to your fix for vite!Commit 1fde536 temporarily fixes the issue. I am currently taking a look at the whole
isProd
/isTest
blunder that creeped in.Anyways, thank you for bringing this to my notice and suggesting changes, @ivorpad !
@patrickbolle transferring this to a separate issue #22