-
Notifications
You must be signed in to change notification settings - Fork 919
yarn update issue #675
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
+1 |
2 similar comments
+1 |
+1 |
Yeah, this causing error in my App since I updated to [email protected] [email protected] Had to disable HMR for now... |
I made a pr to update the dependencies. |
I assume this is because yarn caches dependencies on your machine for some time. you could clean the cache with |
@LinusBorg ok I managed to resolve my previous issue by cleaning yarn cache, removing node_modules/yarn.lock and installing dependencies once again. But I have one more question though. I have disabled production tip in my app via config |
Sorry to say, but I have no idea :D It may have something to do that the HMR API loads vue itself during the replacement process, in somehwere in that proceess the setting gets lost? Maybe open an issue? |
published 11.1.4 with bumped |
When I update vue-loader to the latest (11.1.3), yarn package manager will use vue-hot-reload-api version 2.0.6, not the latest(2.0.11). And it refuse to use the latest vue-hot-reload-api even if I explicitly add it as dependency. This will result in runtime error with latest vue esm runtime.
I know this is probably yarn's issue, but I assume that this can be resolved simply by bump dependencies in package.json?
The text was updated successfully, but these errors were encountered: