Skip to content

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

Closed
steambap opened this issue Feb 27, 2017 · 9 comments
Closed

yarn update issue #675

steambap opened this issue Feb 27, 2017 · 9 comments

Comments

@steambap
Copy link

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?

@rferro
Copy link

rferro commented Feb 27, 2017

+1

2 similar comments
@jialanmo
Copy link

+1

@blade254353074
Copy link

+1

@sqal
Copy link

sqal commented Feb 27, 2017

Yeah, this causing error in my App since I updated to [email protected] [email protected]

img1
img2

Had to disable HMR for now...

@blade254353074
Copy link

blade254353074 commented Feb 27, 2017

I made a pr to update the dependencies.
Waiting for merge or just using npm install vue-hot-reload-api to update vue-hot-reload-api.

@LinusBorg
Copy link
Member

I assume this is because yarn caches dependencies on your machine for some time.

you could clean the cache with yarn cache clean

@sqal
Copy link

sqal commented Feb 27, 2017

@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 Vue.config.productionTip = false but this only works when HMR is disabled. Why is that?

@LinusBorg
Copy link
Member

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?

@yyx990803
Copy link
Member

published 11.1.4 with bumped vue-hot-reload-api version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants