-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Hot reload not triggered if package is installed by CNPM #2284
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
Comments
See: #1559 |
haoqunjiang
added a commit
to haoqunjiang/vue-cli
that referenced
this issue
Aug 31, 2018
Currently in Vue CLI we set the default `symlinks` config to `false`. This setting is counterintuitive, and inconsitent with webpack's default configuration, per https://webpack.js.org/configuration/resolve/#resolve-symlinks The change of default `symlinks` value is introduced by vuejs@5b4df14 It is most likely a duplicate of vuejs@145492b Since several third-party npm clients uses symlinks to speed up installation (e.g. cnpm, pnpm...), that change breaks webpack HMR for their users. See vuejs#1559, vuejs#2195, vuejs#2284 This commit also fixes vuejs#1609
haoqunjiang
added a commit
to haoqunjiang/vue-cli
that referenced
this issue
Aug 31, 2018
Currently in Vue CLI we set the default `symlinks` config to `false`. This setting is counterintuitive, and inconsitent with webpack's default configuration, per https://webpack.js.org/configuration/resolve/#resolve-symlinks The change of default `symlinks` value is introduced by vuejs@5b4df14 It is most likely a duplicate of vuejs@145492b Since several third-party npm clients uses symlinks to speed up installation (e.g. cnpm, pnpm...), that change breaks webpack HMR for their users. See vuejs#1559, vuejs#2195, vuejs#2284 This commit also fixes vuejs#1609
haoqunjiang
added a commit
to haoqunjiang/vue-cli
that referenced
this issue
Sep 3, 2018
Currently in Vue CLI we set the default `symlinks` config to `false`. This setting is counterintuitive, and inconsitent with webpack's default configuration, per https://webpack.js.org/configuration/resolve/#resolve-symlinks The change of default `symlinks` value is introduced by vuejs@5b4df14 It is most likely a duplicate of vuejs@145492b Since several third-party npm clients uses symlinks to speed up installation (e.g. cnpm, pnpm...), that change breaks webpack HMR for their users. See vuejs#1559, vuejs#2195, vuejs#2284 This commit also fixes vuejs#1609
haoqunjiang
added a commit
to haoqunjiang/vue-cli
that referenced
this issue
Sep 4, 2018
Currently in Vue CLI we set the default `symlinks` config to `false`. This setting is counterintuitive, and inconsitent with webpack's default configuration, per https://webpack.js.org/configuration/resolve/#resolve-symlinks The change of default `symlinks` value is introduced by vuejs@5b4df14 It is most likely a duplicate of vuejs@145492b Since several third-party npm clients uses symlinks to speed up installation (e.g. cnpm, pnpm...), that change breaks webpack HMR for their users. See vuejs#1559, vuejs#2195, vuejs#2284 This commit also fixes vuejs#1609
haoqunjiang
added a commit
that referenced
this issue
Sep 5, 2018
Currently in Vue CLI we set the default `symlinks` config to `false`. This setting is counterintuitive, and inconsistent with webpack's default configuration, per https://webpack.js.org/configuration/resolve/#resolve-symlinks The change of default `symlinks` value is introduced by 5b4df14 It is most likely a duplicate of 145492b Since several third-party npm clients uses symlinks to speed up installation (e.g. cnpm, pnpm...), that change breaks webpack HMR for their users. See #1559, #2195, #2284 This commit also fixes #1609
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
3.0.1
Node and OS info
Node 8.11.4 / cnpm 6.0.0 / npm 6.2.0 / MacOS 10.13.6 and Windows 10
Steps to reproduce
What is expected?
Hot reload triggered after file been changed
What is actually happening?
While recompiling triggered correctly, the page isn't automaticly reload. Maybe there's an issue about package dependencies.
The text was updated successfully, but these errors were encountered: