webpack-dev-server: command not found error [Solved]

avatar

Borislav Hadzhiev

Last updated: Feb 27, 2022

banner

Photo from Unsplash

webpack-dev-server: command not found error [Solved] #

To solve the error "webpack-dev-server: command not found", install the package globally by running npm install -g webpack-dev-server 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.

command not found webpack dev server

Open your terminal and install webpack-dev-server globally by running the following command.

shell
# 👇️ install webpack-dev-server globally npm install -g webpack-dev-server # 👇️ install webpack-dev-server locally to your project npm install webpack-dev-server --save-dev
If the global installation of webpack-dev-server fails, you might have to run the command prefixed with sudo.
shell
# 👇️ if you got permissions error npm install -g webpack-dev-server

Alternatively, you can open your terminal in the directory where your webpack.config.js file is and run the command npx webpack serve.

shell
npx webpack serve --config webpack.config.js
If the "webpack-dev-server: command not found" error is not resolved, try restarting your terminal.

If that doesn't help, run the following command:

shell
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 you add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

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.

For example, on macOS, you can update your path with the following command:

shell
# make sure path matches with npm config get prefix export PATH=/usr/local/share/npm/bin:$PATH

And on Windows, the output of the npm config get prefix command will look something like: C:\Users\Your_User_Name\AppData\Roaming\npm.

Edit the environment variable on your machine and add the specified path (replacing the placeholder with your username).

If you are on Linux, you can add the output from the npm config get prefix command to your .bashrc file.

~/.bashrc
# 👇️ make sure to update the path with the output # from the command export PATH="/usr/local/share/npm/bin:$PATH"
If you add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

If that doesn't help try to reinstall Node.js on your machine and then install webpack-dev-server globally by running npm install -g webpack-dev-server.

During the installation, you might get a prompt for whether you want to automatically update the PATH environment variable on your system, make sure to tick the option.
shell
# 👇️ install webpack-dev-server globally npm install -g webpack-dev-server
If the global installation of webpack-dev-server fails, you might have to run the command prefixed with sudo.
shell
# 👇️ if you got permissions error sudo npm install -g webpack-dev-server

Alternatively, you can see how you can fix the permissions error on this page in the official npm docs.

Conclusion #

To solve the error "webpack-dev-server: command not found", install the package globally by running npm install -g webpack-dev-server 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.

I wrote a book in which I share everything I know about how to become a better, more efficient programmer.
book cover
You can use the search field on my Home Page to filter through all of my articles.