Mismatch vue package error in nuxtjs
0
I am getting an error while trying to run my project on dev mode.
user@Apples-MacBook-Pro myproject (hotfix/carousel-2) $ npm run dev
> myproject@1.0.0 dev /Users/user/nuxt-projects/myproject
> nuxt
/Users/user/nuxt-projects/myproject/node_modules/vue-server-renderer/index.js:8
throw new Error(
^
Error:
Vue packages version mismatch:
- vue@2.5.16
- vue-server-renderer@2.5.13
I tried deleting the node_modules directory and re-run npm insatll, but still getting the same error. Could you please point me to the right direction?
node.js vue.js nuxt.js
edited Jul 23 '18 at 14:15
v-gael
1279
asked Jul 23 '18 at 9:55
Benjamin Smith MaxBenjamin Smith Max
71411435
add a comment |
0
I am getting an error while trying to run my project on dev mode.
user@Apples-MacBook-Pro myproject (hotfix/carousel-2) $ npm run dev
> myproject@1.0.0 dev /Users/user/nuxt-projects/myproject
> nuxt
/Users/user/nuxt-projects/myproject/node_modules/vue-server-renderer/index.js:8
throw new Error(
^
Error:
Vue packages version mismatch:
- vue@2.5.16
- vue-server-renderer@2.5.13
I tried deleting the node_modules directory and re-run npm insatll, but still getting the same error. Could you please point me to the right direction?
node.js vue.js nuxt.js
edited Jul 23 '18 at 14:15
v-gael
1279
asked Jul 23 '18 at 9:55
Benjamin Smith MaxBenjamin Smith Max
71411435
1
change version ofvue-server-rendererto 2.5.16 manually.
– Max Sinev
Jul 23 '18 at 10:15
Do u have vue-server-render in your package.json? Deleting it should work
– Aldarund
Jul 23 '18 at 23:17
add a comment |
0
0
0
I am getting an error while trying to run my project on dev mode.
user@Apples-MacBook-Pro myproject (hotfix/carousel-2) $ npm run dev
> myproject@1.0.0 dev /Users/user/nuxt-projects/myproject
> nuxt
/Users/user/nuxt-projects/myproject/node_modules/vue-server-renderer/index.js:8
throw new Error(
^
Error:
Vue packages version mismatch:
- vue@2.5.16
- vue-server-renderer@2.5.13
I tried deleting the node_modules directory and re-run npm insatll, but still getting the same error. Could you please point me to the right direction?
node.js vue.js nuxt.js
edited Jul 23 '18 at 14:15
v-gael
1279
asked Jul 23 '18 at 9:55
Benjamin Smith MaxBenjamin Smith Max
71411435
I am getting an error while trying to run my project on dev mode.
user@Apples-MacBook-Pro myproject (hotfix/carousel-2) $ npm run dev
> myproject@1.0.0 dev /Users/user/nuxt-projects/myproject
> nuxt
/Users/user/nuxt-projects/myproject/node_modules/vue-server-renderer/index.js:8
throw new Error(
^
Error:
Vue packages version mismatch:
- vue@2.5.16
- vue-server-renderer@2.5.13
I tried deleting the node_modules directory and re-run npm insatll, but still getting the same error. Could you please point me to the right direction?
node.js vue.js nuxt.js
node.js vue.js nuxt.js
edited Jul 23 '18 at 14:15
v-gael
1279
asked Jul 23 '18 at 9:55
Benjamin Smith MaxBenjamin Smith Max
71411435
edited Jul 23 '18 at 14:15
v-gael
1279
asked Jul 23 '18 at 9:55
Benjamin Smith MaxBenjamin Smith Max
71411435
edited Jul 23 '18 at 14:15
v-gael
1279
edited Jul 23 '18 at 14:15
v-gael
1279
edited Jul 23 '18 at 14:15
v-gael
1279
1279
asked Jul 23 '18 at 9:55
Benjamin Smith MaxBenjamin Smith Max
71411435
asked Jul 23 '18 at 9:55
Benjamin Smith MaxBenjamin Smith Max
71411435
asked Jul 23 '18 at 9:55
Benjamin Smith MaxBenjamin Smith Max
71411435
71411435
1
change version ofvue-server-rendererto 2.5.16 manually.
– Max Sinev
Jul 23 '18 at 10:15
Do u have vue-server-render in your package.json? Deleting it should work
– Aldarund
Jul 23 '18 at 23:17
add a comment |
1
change version ofvue-server-rendererto 2.5.16 manually.
– Max Sinev
Jul 23 '18 at 10:15
Do u have vue-server-render in your package.json? Deleting it should work
– Aldarund
Jul 23 '18 at 23:17
1
1
change version of
vue-server-renderer to 2.5.16 manually.– Max Sinev
Jul 23 '18 at 10:15
change version of
vue-server-renderer to 2.5.16 manually.– Max Sinev
Jul 23 '18 at 10:15
Do u have vue-server-render in your package.json? Deleting it should work
– Aldarund
Jul 23 '18 at 23:17
Do u have vue-server-render in your package.json? Deleting it should work
– Aldarund
Jul 23 '18 at 23:17
add a comment |
2 Answers
2
active
oldest
votes
0
I solved same problem with deleting cache files and package lock files.
rm -rf package-lock.json && npm cache clean
If you used yarn instead of npm, then
rm -rf yarn.lock && yarn cache clean
After removing lock files, install again
npm install
OR
yarn install --network-timeout 600000
Later, it might solve same problems.
answered Sep 17 '18 at 13:32
luiseokluiseok
1
As ofnpm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use'npm cache verify'instead. On the other hand, if you're debugging an issue with the installer, you can usenpm install --cache /tmp/empty-cacheto use a temporary cache instead of nuking the actual one. If you're sure you want to delete the entire cache, rerun this command with--force.
– Anima-t3d
Nov 13 '18 at 2:11
Unfortunately it did not solve my issue using nuxt.
– Anima-t3d
Nov 13 '18 at 2:12
add a comment |
0
Eventually I got it to work by using:
rm -rf node_modules/// Removes node_modules folder
rm -rf package-lock.json && npm cache clean --force//Removes package-lock file and cleans cache forcefully (npm v5+)
npm install// do a fresh install
Thanks @luiseok
answered Nov 13 '18 at 7:34
Anima-t3dAnima-t3d
1,46111736
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51476023%2fmismatch-vue-package-error-in-nuxtjs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
I solved same problem with deleting cache files and package lock files.
rm -rf package-lock.json && npm cache clean
If you used yarn instead of npm, then
rm -rf yarn.lock && yarn cache clean
After removing lock files, install again
npm install
OR
yarn install --network-timeout 600000
Later, it might solve same problems.
answered Sep 17 '18 at 13:32
luiseokluiseok
1
As ofnpm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use'npm cache verify'instead. On the other hand, if you're debugging an issue with the installer, you can usenpm install --cache /tmp/empty-cacheto use a temporary cache instead of nuking the actual one. If you're sure you want to delete the entire cache, rerun this command with--force.
– Anima-t3d
Nov 13 '18 at 2:11
Unfortunately it did not solve my issue using nuxt.
– Anima-t3d
Nov 13 '18 at 2:12
add a comment |
0
I solved same problem with deleting cache files and package lock files.
rm -rf package-lock.json && npm cache clean
If you used yarn instead of npm, then
rm -rf yarn.lock && yarn cache clean
After removing lock files, install again
npm install
OR
yarn install --network-timeout 600000
Later, it might solve same problems.
answered Sep 17 '18 at 13:32
luiseokluiseok
1
As ofnpm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use'npm cache verify'instead. On the other hand, if you're debugging an issue with the installer, you can usenpm install --cache /tmp/empty-cacheto use a temporary cache instead of nuking the actual one. If you're sure you want to delete the entire cache, rerun this command with--force.
– Anima-t3d
Nov 13 '18 at 2:11
Unfortunately it did not solve my issue using nuxt.
– Anima-t3d
Nov 13 '18 at 2:12
add a comment |
0
0
0
I solved same problem with deleting cache files and package lock files.
rm -rf package-lock.json && npm cache clean
If you used yarn instead of npm, then
rm -rf yarn.lock && yarn cache clean
After removing lock files, install again
npm install
OR
yarn install --network-timeout 600000
Later, it might solve same problems.
answered Sep 17 '18 at 13:32
luiseokluiseok
1
I solved same problem with deleting cache files and package lock files.
rm -rf package-lock.json && npm cache clean
If you used yarn instead of npm, then
rm -rf yarn.lock && yarn cache clean
After removing lock files, install again
npm install
OR
yarn install --network-timeout 600000
Later, it might solve same problems.
answered Sep 17 '18 at 13:32
luiseokluiseok
1
answered Sep 17 '18 at 13:32
luiseokluiseok
1
answered Sep 17 '18 at 13:32
luiseokluiseok
1
answered Sep 17 '18 at 13:32
luiseokluiseok
1
1
As ofnpm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use'npm cache verify'instead. On the other hand, if you're debugging an issue with the installer, you can usenpm install --cache /tmp/empty-cacheto use a temporary cache instead of nuking the actual one. If you're sure you want to delete the entire cache, rerun this command with--force.
– Anima-t3d
Nov 13 '18 at 2:11
Unfortunately it did not solve my issue using nuxt.
– Anima-t3d
Nov 13 '18 at 2:12
add a comment |
As ofnpm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use'npm cache verify'instead. On the other hand, if you're debugging an issue with the installer, you can usenpm install --cache /tmp/empty-cacheto use a temporary cache instead of nuking the actual one. If you're sure you want to delete the entire cache, rerun this command with--force.
– Anima-t3d
Nov 13 '18 at 2:11
Unfortunately it did not solve my issue using nuxt.
– Anima-t3d
Nov 13 '18 at 2:12
As of
npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use npm install --cache /tmp/empty-cache to use a temporary cache instead of nuking the actual one. If you're sure you want to delete the entire cache, rerun this command with --force.– Anima-t3d
Nov 13 '18 at 2:11
As of
npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use npm install --cache /tmp/empty-cache to use a temporary cache instead of nuking the actual one. If you're sure you want to delete the entire cache, rerun this command with --force.– Anima-t3d
Nov 13 '18 at 2:11
Unfortunately it did not solve my issue using nuxt.
– Anima-t3d
Nov 13 '18 at 2:12
Unfortunately it did not solve my issue using nuxt.
– Anima-t3d
Nov 13 '18 at 2:12
add a comment |
0
Eventually I got it to work by using:
rm -rf node_modules/// Removes node_modules folder
rm -rf package-lock.json && npm cache clean --force//Removes package-lock file and cleans cache forcefully (npm v5+)
npm install// do a fresh install
Thanks @luiseok
answered Nov 13 '18 at 7:34
Anima-t3dAnima-t3d
1,46111736
add a comment |
0
Eventually I got it to work by using:
rm -rf node_modules/// Removes node_modules folder
rm -rf package-lock.json && npm cache clean --force//Removes package-lock file and cleans cache forcefully (npm v5+)
npm install// do a fresh install
Thanks @luiseok
answered Nov 13 '18 at 7:34
Anima-t3dAnima-t3d
1,46111736
add a comment |
0
0
0
Eventually I got it to work by using:
rm -rf node_modules/// Removes node_modules folder
rm -rf package-lock.json && npm cache clean --force//Removes package-lock file and cleans cache forcefully (npm v5+)
npm install// do a fresh install
Thanks @luiseok
answered Nov 13 '18 at 7:34
Anima-t3dAnima-t3d
1,46111736
Eventually I got it to work by using:
rm -rf node_modules/// Removes node_modules folder
rm -rf package-lock.json && npm cache clean --force//Removes package-lock file and cleans cache forcefully (npm v5+)
npm install// do a fresh install
Thanks @luiseok
answered Nov 13 '18 at 7:34
Anima-t3dAnima-t3d
1,46111736
answered Nov 13 '18 at 7:34
Anima-t3dAnima-t3d
1,46111736
answered Nov 13 '18 at 7:34
Anima-t3dAnima-t3d
1,46111736
answered Nov 13 '18 at 7:34
Anima-t3dAnima-t3d
1,46111736
1,46111736
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51476023%2fmismatch-vue-package-error-in-nuxtjs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
change version of
vue-server-rendererto 2.5.16 manually.– Max Sinev
Jul 23 '18 at 10:15
Do u have vue-server-render in your package.json? Deleting it should work
– Aldarund
Jul 23 '18 at 23:17