Brtdku

Better solution to this problem is to install Webpack globally.

This always works and it worked for me. Try below command.

npm install -g webpack

As an alternative, if you have Webpack installed locally, you can explicitly specify where Command Prompt should look to find it, like so:

node_modules.binwebpack

(This does assume that you're inside the directory with your package.json and that you've already run npm install webpack.)

npm install -g webpack-dev-server will solve your issue

Add webpack command as an npm script in your package.json.

{

    "name": "react-app",

    "version": "1.0.0",

    "scripts": {

      "compile": "webpack --config webpack.config.js"

    }

}

Then run

npm run compile

When the webpack is installed it creates a binary in ./node_modules/.bin folder. npm scripts also looks for executable created in this folder

Webpack CLI is now in a separate package and must be installed globally in order to use the 'webpack' command:

npm install -g webpack-cli

Just run your command line (cmd) as an administrator.

I've had same issue and just added the code block into my package.json file;

 "scripts": {

   "build": "webpack -d --progress --colors"

 }

and then run command on terminal;

npm run build

Try deleting node_modules in local directory and re-run npm install.

you have to install webpack and webpack-cli in the same scope.

npm i -g webpack webpack-cli

or,

npm i webpack webpack-cli

if you install it locally you need to call it specifially

node_modules/.bin/webpack -v

I got the same error, none of the solutions worked for me, I reinstalled node and that repaired my environment, everything works again.

We also experienced this problem and I like all the answers that suggest using a script defined in package.json.

For our solutions we often use the following sequence:

1. 
   npm install --save-dev webpack-cli (if you're using webpack v4 or later, otherwise use npm install --save-dev webpack, see webpack installation, retrieved 19 Jan 2019)


2. npx webpack

Step 1 is a one-off. Step 2 also checks ./node_modules/.bin. You can add the second step as a npm script to package.json as well, for example:

{

   ...

   "scripts": {

      ...

      "build": "npx webpack --mode development",

      ...

   },

   ...

}

and then use npm run build to execute this script.

Tested this solution with npm version 6.5.0, webpack version 4.28.4 and webpack-cli version 3.2.1 on Windows 10, executing all commands inside of a PowerShell window. My nodejs version is/was 10.14.2. I also tested this on Ubuntu Linux version 18.04.

I'd advise against installing webpack globally, in particular if you are working with a lot of different projects each of which may require a different version of webpack. Installing webpack globally locks you down to a particular version across all projects on the same machine.

Sometimes npm install -g webpack does not save properly. Better to use npm install webpack --save . It worked for me.