Troubleshooting for Windows, when vue command doesn't work #6245
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After installing vue\cli, if the >vue command doesn't work, it could be because the npm path is not in the Windows system path.
stritti
reviewed
Jan 29, 2021
|
|
||
| ::: 'vue' is not recognized as an internal or external command | ||
| This error happens in Windows if you don't have npm in your system path. To check: from a command prompt type `path`. | ||
| Confirm the actual path to your npm repo. It should be like `c:\Users\[YourLoginName]\AppData\Roaming\npm` (using your actual login name). Add that to your System Properties, Environment Variables. |
There was a problem hiding this comment.
You get this path by using command: > npm config get prefix
Had this problem yesterday too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After installing vue\cli, if the >vue command doesn't work, it could be because the npm path is not in the Windows system path.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information: