Troubleshooting
This document covers some common Vue CLI issues and how to resolve them. You should always follow these steps before opening a new issue.
sudo
or as root
Running installation with If you install @vue/cli-service
as root
user or with sudo
, there might be issues when running package postinstall
scripts.
This is a security feature of npm. You should always avoid running npm with root privileges because install scripts can be unintentionally malicious.
If you must however, you can workaround this error by setting the --unsafe-perm
flag of npm. This can be done by prefixing the command with an environment variable, i.e.
npm_config_unsafe_perm=true vue create my-project
node_modules
Symbolic Links in 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, thus breaks ESLint / Babel config lookup.
A workaround for this issue is to manually disable symlinks resolution in webpack:
// vue.config.js
module.exports = {
chainWebpack: (config) => {
config.resolve.symlinks(false)
}
}
Disabling resolve.symlinks
may break hot module reloading if your dependencies are installed by third-party npm clients that utilized symbolic links, such ascnpm
or pnpm
.