Skip to content

HMR does not work when node_modules is a symlink #1609

Closed
@tmcdos

Description

@tmcdos

Version

3.0.0-rc.3

Reproduction link

https://github.com/tmcdos/vuecli/tree/master

Steps to reproduce

Create a fresh project with "vue create myproject"
Make the "node_modules" a symlink - e.g. from "d:\work\myproject\node_modules" to "e:\node_modules" (which is a RAM-disk)
Start the development server with "npm run serve"
Open the project in your favorite browser - http://localhost:8080
Try to change something in Home.vue component

What is expected?

The browser must hot-reload the changes - because it is clearly seen on the console that any change in the source code is noticed by the webpack's file watcher and the application is immediately rebuild (showing the errors, if any).

What is actually happening?

You will see the project being rebuilt in the console - however no hot-reload will happen in the browser.
WebSocket listener receives information about the new bundle name(s) - but does not issue AJAX call(s) to fetch the new code.


I am also using this approach (with a symlink for node_modules to a RAM-disk) with the old Vue-CLI 2.9.6 and it works perfectly fine.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions