-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hot reload and changes not taken into account when editing a package in node_modules folder #9626
Comments
Try this: devServer: {
https: false,
port: 8080,
open: false,
watch: true,
watchOptions: {
ignored: [
/node_modules([\\]+|\/)+(?!my-package-name)/
]
},
}, Ignores everything under node_modules except the targeted |
@sebastien-vedrine |
@hawkeye64 |
@sebastien-vedrine I don't think it'll be fixed until early next week |
Okay that would be nice, thank you! |
There is no fix that we can do because this is a webpack v5 issue and outside of our reach. Everything under quasar.conf.js > devServer is passed to webpack-dev-server. Please open a ticket on https://github.com/webpack/webpack-dev-server and mention it's for v4.0.0-beta.3 |
I just installed a new Quasar v2 (rc-1 build) app.
After running
quasar dev
, when I edit my files in thesrc
directory, the live reload happens with the latest modifications.However when editing my dependency files (in
node_modules
) for dev purposes, the console warned me that the webpack-dev-server hot reloads but my components don't re-render and all my changes are not taken into account (even if I refresh the whole page).This is what's displayed in the console when editing a file in a
node_modules
package (hot reload not working):When editing an
src
file (hot reload working):In my previous Quasar v1 projects, I never encountered this issue. I was able to change any file in the
node_modules
folder and had hot reload working (without any specific configuration).I've tried to add this config I found here
I'm aware this config is made for quasar extensions, but I think it should still work with any
node_modules
.But an error occurs stating that watchOptions does not match the API schema (when running
quasar dev
)To Reproduce
Steps to reproduce the behavior:
Platform (please complete the following information):
Quasar Version: v.2.0.0-rc1
@quasar/app Version: ^3.0.0-beta.1
Quasar mode:
Tested on:
OS: debian
Node: v14.16.1
NPM: 6.14.12
Yarn: 1.22.10
Browsers: Google Chrome
The text was updated successfully, but these errors were encountered: