Last updated: Apr 4, 2024
Reading timeยท7 min

To solve the error "'vue-cli-service' is not recognized as an internal or
external command, operable program or batch file", install the
@vue/cli-service package globally by running npm install -g @vue/cli-service
and clear your npm cache.
First, open your terminal in your project's root directory (where your
package.json) file is and run npm install.
npm install npm run serve
If the error is not resolved, try to delete your node_modules and
package-lock.json (not
package.json) files and re-run npm install.
If you are on macOS or Linux, issue the following commands in bash or zsh.
# for macOS and Linux rm -rf node_modules rm -f package-lock.json rm -f yarn.lock # ๐๏ธ clean npm cache npm cache clean --force # ๐๏ธ install packages npm install
If you are on Windows, issue the following commands in CMD.
# for Windows rd /s /q "node_modules" del package-lock.json del -f yarn.lock # ๐๏ธ clean npm cache npm cache clean --force # ๐๏ธ install packages npm install
If that didn't help, install @vue/cli-service globally by running the following command.
# ๐๏ธ Uninstall old vue cli npm uninstall vue-cli -g # ๐๏ธ install @vue/cli-service and @vue/cli globally npm install -g @vue/cli-service npm install -g @vue/cli npm run serve

If the global installation of @vue/cli-service fails, you have to open your
shell as an administrator or run the command prefixed with
sudo.
# ๐๏ธ Uninstall old vue cli sudo npm uninstall vue-cli -g # ๐๏ธ install @vue/cli-service and @vue/cli globally sudo npm install -g @vue/cli-service sudo npm install -g @vue/cli npm run serve
Make sure your shell is opened at the root directory of your project (where your
package.json file is) when running the npm run serve command.
After installing @vue/cli-service globally and running npm install to
install the dependencies in your package.json file, the error should be
resolved.
To solve the error "'vue' is not recognized as an internal or external
command, operable program or batch file", install the @vue/cli package
globally by running npm install -g @vue/cli, restart your terminal and make
sure your PATH environment variable is set up correctly.
Open your terminal and install the vue cli globally by running the following command.
# ๐๏ธ Uninstall old vue cli npm uninstall vue-cli -g # ๐๏ธ install @vue/cli globally npm install -g @vue/cli # ๐๏ธ if command outputs version, vue is installed vue --version # ๐๏ธ Create a vue project vue create my-project
If the vue --version command outputs a version number, then vue is installed
successfully.
vue fails, you have to open your shell as an administrator or run the command prefixed with sudo.# ๐๏ธ if you got permissions error sudo npm uninstall vue-cli -g sudo npm install -g @vue/cli vue --version vue create my-project
If that doesn't help, try to uninstall @vue/cli, install the latest version
and restart your terminal.
# ๐๏ธ if permissions error, prefix with sudo npm uninstall -g @vue/cli # ๐๏ธ if permissions error, prefix with sudo npm install -g @vue/cli@latest vue --version
If that didn't help, run the following command:
npm config get prefix
The command will show you the path where
npm puts your
globally installed packages. The global packages will be in the bin directory
at the specified path.
Look at the PATH environment variable on your operating system and add the
path that the npm config get prefix command outputs if it's not already
there.
On Windows, the output of the npm config get prefix command will look
something like: C:\Users\Your_User_Name\AppData\Roaming\npm.
To update the PATH on a Windows machine, you have to:
env and then click "Edit the system
environment variables"Path variable and add the output you got from the
npm config get prefix command.The path should look like C:\Users\Your_User_Name\AppData\Roaming\npm (make
sure to replace the Your_User_name placeholder with your actual username).
If you get the error "vue cannot be loaded because running scripts is disabled on this system", open your PowerShell as an administrator and set its execution policy with the Set-ExecutionPolicy command.
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Set-ExecutionPolicy command.This effectively removes the execution policy of Restricted, which doesn't
allow us to load configuration files or run scripts. The Restricted execution
policy is the default for Windows client computers.
If you are on macOS, you can update your path with the following command:
# make sure path matches with npm config get prefix export PATH=/usr/local/share/npm/bin:$PATH
If you are on Linux, you can add the output from the npm config get prefix
command to your .bashrc file.
# ๐๏ธ make sure to update the path with the output # from the command export PATH="/usr/local/share/npm/bin:$PATH"
If that doesn't help try to reinstall Node.js on your
machine and then install vue globally by running npm install -g @vue/cli.
# ๐๏ธ install @vue/cli globally npm install -g @vue/cli # ๐๏ธ if command outputs version, vue is installed vue --version # ๐๏ธ Create a vue project vue create my-project
vue fails, you have to open your shell as an administrator or run the command prefixed with sudo.# ๐๏ธ if you got permissions error sudo npm install -g @vue/cli vue --version vue create my-project
Alternatively, you can see how you can fix the permissions error on this page in the official npm docs.
To solve the error "vue: command not found", install the @vue/cli package
globally by running npm install -g @vue/cli and restart your terminal.
If the command fails, run it with sudo and make sure the correct PATH is set
in your system's environment variable.

Open your terminal and install the vue cli globally by running the following command.
# ๐๏ธ Uninstall old vue cli npm uninstall vue-cli -g # ๐๏ธ install @vue/cli globally npm install -g @vue/cli # ๐๏ธ if command outputs version, vue is installed vue --version # ๐๏ธ Create a vue project vue create my-project
If the vue --version command outputs a version number, then vue is installed
successfully.
vue fails, you might have to run the command prefixed with sudo.# ๐๏ธ if you got permissions error sudo npm uninstall vue-cli -g sudo npm install -g @vue/cli vue --version vue create my-project
If that doesn't help, try to uninstall @vue/cli, install the latest version
and restart your terminal.
# ๐๏ธ if permissions error, prefix with sudo npm uninstall -g @vue/cli # ๐๏ธ if permissions error, prefix with sudo npm install -g @vue/cli@latest vue --version
If that doesn't help either, run the following command:
npm config get prefix
The command will show you the path where npm puts your globally installed
packages. The global packages will be in the bin directory at the specified
path.
Look at the PATH environment variable on your operating system and add the
path that the npm config get prefix command outputs if it's not already
there.
If that didn't work, try to add the path to the bin folder (from
npm config get prefix) to your PATH environment variable and restart your
terminal.
On macOS, you can update your path with the following command:
# make sure path matches with npm config get prefix export PATH=/usr/local/share/npm/bin:$PATH
Edit the environment variable on your machine and add the specified path (replacing the placeholder with your username).
On Linux, you can add the output from the npm config get prefix command to
your .bashrc file.
# ๐๏ธ make sure to update the path with the output # from the command export PATH="/usr/local/share/npm/bin:$PATH"
If that doesn't help try to reinstall Node.js on your machine and then install
the Vue CLI globally by running npm install -g @vue/cli.
# ๐๏ธ install @vue/cli globally npm install -g @vue/cli # ๐๏ธ if command outputs version, vue is installed vue --version # ๐๏ธ Create a vue project vue create my-project
vue fails, you might have to run the command prefixed with sudo.# ๐๏ธ if you got permissions error sudo npm install -g @vue/cli vue --version vue create my-project
Alternatively, you can see how you can fix the permissions error on this page in the official npm docs.
You can learn more about the related topics by checking out the following tutorials: