with-yarn-workspace doesn't Hot Reload changes from another package even after yarn already updated dependency
See original GitHub issuenpm init next-app --example with-yarn-workspaces with-yarn-workspaces-app
yarn dev
- open browser,
foo
is there - open
packages/foo/index.js
, changemodule.exports = "foo";
tomodule.exports = "foo12";
- yarn updated
foo
in top-levelnode_modules
folder tofoo12
- check the browser, still
foo
- refresh the browser, still
foo
- re-run
next dev
, check browser,foo12
finally shows up.
Expect:
Update packages/foo/index.js
should trigger hot reload without re-running next dev
Issue Analytics
- State:
- Created 3 years ago
- Reactions:10
- Comments:19 (13 by maintainers)
Top Results From Across the Web
Hot Reload is not working in my React App - Stack Overflow
To solve the problem in hot reloading/fast_refresh I simply add CHOKIDAR_USEPOLLING=true in package.json:
Read more >XAML Hot Reload for Xamarin.Forms - Microsoft Learn
Reload changes to your XAML file instantly on your running application so you don't have to build your Xamarin.Forms project after every ...
Read more >Yarn lock: how it works and what you risk without maintaining ...
If you've ever built an npm library you might have stumbled across a problem with outdated or randomly updated sub dependencies.
Read more >Plug'n'Play | Yarn - Package Manager
An overview of Plug'n'Play, a powerful and innovative installation strategy for Node.
Read more >WebDev 101: How to use npm and Yarn | Unicorn Utterances
On Node 12, when you switch to Node 14, and attempt to run a create-react-app command, you'll find yourself with a "cannot find...
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
This is not a Next.js bug, this can be closed.
You can follow the progress on this issue on the
next-transpile-modules
repo. 😉V5 will probably get released this week, and should fix it.
Just install from mine @module-federation/next-transpile-modules