[go: nahoru, domu]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Troubleshooting for Windows, when vue command doesn't work #6245

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Troubleshooting for Windows, when vue command doesn't work #6245

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/guide/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ npm_config_unsafe_perm=true vue create my-project

## Symbolic Links in `node_modules`

If there're dependencies installed by `npm link` or `yarn link`, ESLint (and sometimes Babel as well) may not work properly for those symlinked dependencies. It is because [webpack resolves symlinks to their real locations by default](https://webpack.js.org/configuration/resolve/#resolvesymlinks), thus breaks ESLint / Babel config lookup.
If there are dependencies installed by `npm link` or `yarn link`, ESLint (and sometimes Babel as well) may not work properly for those symlinked dependencies. It is because [webpack resolves symlinks to their real locations by default](https://webpack.js.org/configuration/resolve/#resolvesymlinks), thus breaks ESLint / Babel config lookup.

A workaround for this issue is to manually disable symlinks resolution in webpack:

Expand All @@ -31,3 +31,7 @@ module.exports = {

::: warning
Disabling `resolve.symlinks` may break hot module reloading if your dependencies are installed by third-party npm clients that utilized symbolic links, such as`cnpm` or `pnpm`.

::: '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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You get this path by using command: > npm config get prefix

Had this problem yesterday too.