Vue Cli 3 updating Issue [closed]











up vote
2
down vote

favorite












Terminal



Terminal



When I go to remove the cli from the global packages it doesn't seem to work in the way expected. When I go to update the cli it works, but when I try and create a new project it asks me to install it again. When I check the version I have it tells me I already have a later version than what I tried to install. I have tried a couple different ways to get it to remove the old package but have received nothing but more headaches. Any ideas?










share|improve this question















closed as off-topic by user6655984, Graham, Shiladitya, Unheilig, EdChum Nov 9 at 9:42


This question appears to be off-topic. The users who voted to close gave these specific reasons:



  • "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Unheilig, EdChum

  • "Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example." – Community, Graham, Shiladitya


If this question can be reworded to fit the rules in the help center, please edit the question.













  • Are you using nvm to manage Node versions? If so, does this help?
    – Phil
    Nov 8 at 22:33












  • I will look into it currently not using nvm.
    – daniel R
    Nov 8 at 23:25






  • 1




    I found the issue i was using a old version of node. You got me thinking and it led me to the answer thank you!
    – daniel R
    Nov 9 at 0:05















up vote
2
down vote

favorite












Terminal



Terminal



When I go to remove the cli from the global packages it doesn't seem to work in the way expected. When I go to update the cli it works, but when I try and create a new project it asks me to install it again. When I check the version I have it tells me I already have a later version than what I tried to install. I have tried a couple different ways to get it to remove the old package but have received nothing but more headaches. Any ideas?










share|improve this question















closed as off-topic by user6655984, Graham, Shiladitya, Unheilig, EdChum Nov 9 at 9:42


This question appears to be off-topic. The users who voted to close gave these specific reasons:



  • "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Unheilig, EdChum

  • "Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example." – Community, Graham, Shiladitya


If this question can be reworded to fit the rules in the help center, please edit the question.













  • Are you using nvm to manage Node versions? If so, does this help?
    – Phil
    Nov 8 at 22:33












  • I will look into it currently not using nvm.
    – daniel R
    Nov 8 at 23:25






  • 1




    I found the issue i was using a old version of node. You got me thinking and it led me to the answer thank you!
    – daniel R
    Nov 9 at 0:05













up vote
2
down vote

favorite









up vote
2
down vote

favorite











Terminal



Terminal



When I go to remove the cli from the global packages it doesn't seem to work in the way expected. When I go to update the cli it works, but when I try and create a new project it asks me to install it again. When I check the version I have it tells me I already have a later version than what I tried to install. I have tried a couple different ways to get it to remove the old package but have received nothing but more headaches. Any ideas?










share|improve this question















Terminal



Terminal



When I go to remove the cli from the global packages it doesn't seem to work in the way expected. When I go to update the cli it works, but when I try and create a new project it asks me to install it again. When I check the version I have it tells me I already have a later version than what I tried to install. I have tried a couple different ways to get it to remove the old package but have received nothing but more headaches. Any ideas?







macos vue.js vue-cli-3






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 9 at 0:03









Gino Mempin

1,43661725




1,43661725










asked Nov 8 at 21:19









daniel R

112




112




closed as off-topic by user6655984, Graham, Shiladitya, Unheilig, EdChum Nov 9 at 9:42


This question appears to be off-topic. The users who voted to close gave these specific reasons:



  • "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Unheilig, EdChum

  • "Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example." – Community, Graham, Shiladitya


If this question can be reworded to fit the rules in the help center, please edit the question.




closed as off-topic by user6655984, Graham, Shiladitya, Unheilig, EdChum Nov 9 at 9:42


This question appears to be off-topic. The users who voted to close gave these specific reasons:



  • "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Unheilig, EdChum

  • "Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example." – Community, Graham, Shiladitya


If this question can be reworded to fit the rules in the help center, please edit the question.












  • Are you using nvm to manage Node versions? If so, does this help?
    – Phil
    Nov 8 at 22:33












  • I will look into it currently not using nvm.
    – daniel R
    Nov 8 at 23:25






  • 1




    I found the issue i was using a old version of node. You got me thinking and it led me to the answer thank you!
    – daniel R
    Nov 9 at 0:05


















  • Are you using nvm to manage Node versions? If so, does this help?
    – Phil
    Nov 8 at 22:33












  • I will look into it currently not using nvm.
    – daniel R
    Nov 8 at 23:25






  • 1




    I found the issue i was using a old version of node. You got me thinking and it led me to the answer thank you!
    – daniel R
    Nov 9 at 0:05
















Are you using nvm to manage Node versions? If so, does this help?
– Phil
Nov 8 at 22:33






Are you using nvm to manage Node versions? If so, does this help?
– Phil
Nov 8 at 22:33














I will look into it currently not using nvm.
– daniel R
Nov 8 at 23:25




I will look into it currently not using nvm.
– daniel R
Nov 8 at 23:25




1




1




I found the issue i was using a old version of node. You got me thinking and it led me to the answer thank you!
– daniel R
Nov 9 at 0:05




I found the issue i was using a old version of node. You got me thinking and it led me to the answer thank you!
– daniel R
Nov 9 at 0:05

















active

oldest

votes






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes

Popular posts from this blog

Guess what letter conforming each word

Port of Spain

Run scheduled task as local user group (not BUILTIN)