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
Please paste the results of webpack-cli info here, and mention other relevant information
Expected Behavior
When writing the console.log code in the "node_modules/js-base64/base64.mjs" file, changes are detected and the screen is automatically updated.
Actual Behavior
A change is detected and a new build is made, but the console says "[webpack-dev-server] Nothing changed."
Also, the screen is not updated.
After ending the process, you must restart it for the changes to take effect.
For Bugs; How can we reproduce the behavior?
It is reproduced by writing the console.log code in the file "node_modules/js-base64/base64.mjs".
For Features; What is the motivation and/or use-case for the feature?
I frequently modify the files in the "node_modules" path for debugging. Through the link "#1970", I know that it supports change detection of the path under "node_modules" by default.
But the actual behavior is not working as I wish.
Can you help me? Thank you.
The text was updated successfully, but these errors were encountered:
Expected, this is to improve performance, please read this webpack/webpack#11612, you can set snapshot.managedPaths: [], but it is not recommended, feel free to feedback
Expected, this is to improve performance, please read this webpack/webpack#11612, you can set snapshot.managedPaths: [], but it is not recommended, feel free to feedback
Operating System: Windows 10 Pro
Node Version: 14.16.1
NPM Version: 6.14.12
webpack Version: 5.37.1
webpack-dev-server Version: 4.0.0-beta.3
Code
Please paste the results of
webpack-cli info
here, and mention other relevant informationExpected Behavior
When writing the console.log code in the "node_modules/js-base64/base64.mjs" file, changes are detected and the screen is automatically updated.
Actual Behavior
A change is detected and a new build is made, but the console says "[webpack-dev-server] Nothing changed."
Also, the screen is not updated.
After ending the process, you must restart it for the changes to take effect.
For Bugs; How can we reproduce the behavior?
It is reproduced by writing the console.log code in the file "node_modules/js-base64/base64.mjs".
For Features; What is the motivation and/or use-case for the feature?
I frequently modify the files in the "node_modules" path for debugging. Through the link "#1970", I know that it supports change detection of the path under "node_modules" by default.
But the actual behavior is not working as I wish.
Can you help me? Thank you.
The text was updated successfully, but these errors were encountered: