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
I have searched the issues of this repository and believe that this is not a duplicate.
Expected Behavior
When I change javascript files inside node_modules folder, the related bundles should get recompiled.
Current Behavior
I have to restart next server to get the javascript file inside node_modules recompiled.
Context
I'm sure that webpack watch mode and webpack-dev-middleware have support for recompile bundle whenever any related javascript file changes, but it looks like next disables that and use watcher of itself instead.
This behaviour makes debug by tweak code in node_modules very painful.
Your Environment
Tech
Version
next
4.1.3
node
8.5
OS
MacOS
browser
any
etc
The text was updated successfully, but these errors were encountered:
chemzqm
changed the title
Next.js not watching file changes of node_modules folder
Next.js not watching file changes inside node_modules folder
Oct 25, 2017
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
lockbot
locked as resolved and limited conversation to collaborators
May 10, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected Behavior
When I change javascript files inside node_modules folder, the related bundles should get recompiled.
Current Behavior
I have to restart next server to get the javascript file inside node_modules recompiled.
Context
I'm sure that webpack watch mode and webpack-dev-middleware have support for recompile bundle whenever any related javascript file changes, but it looks like next disables that and use watcher of itself instead.
This behaviour makes debug by tweak code in node_modules very painful.
Your Environment
The text was updated successfully, but these errors were encountered: