Error: Cannot find module 'webpack/lib/node/NodeTemplatePlugin'

Question

Got this Error after running webpack. Webpack is installed globally and I'm running Node

PS D:\Projects\ng2-admin-master> ng serve
Cannot find module 'webpack/lib/node/NodeTemplatePlugin'
Error: Cannot find module 'webpack/lib/node/NodeTemplatePlugin'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (D:\Projects\ng2-admin-master\node_modules\html-webpack-plugin\lib\compiler.js:11:26)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (D:\Projects\ng2-admin-master\node_modules\html-webpack-plugin\index.js:7:21)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
PS D:\Projects\ng2-admin-master>

What is the most frustrating thing is such type of crap happened absolutely for no reason. I didn't install anything new or changed the configuration. Today, it just stopped working. — mimic
– mimic, Commented Feb 14, 2021 at 17:51

General Grievance · Accepted Answer · 2022-03-16 01:23:57Z

88

Update (Apr 2018)

Webpack 4 onwards you are required to install webpack-cli. You may also want to install webpack-dev-middleware if you need to use the options marked with a key on this page.

In this case the command to install is:

npm install --save-dev webpack webpack-cli html-webpack-plugin webpack-dev-server webpack-dev-middleware

As mentioned above, webpack-dev-middleware should be optionally added based on your requirements.

Older answer

Node requires you to install webpack to your project.

You have 2 options to solve the above:

Remove global webpack and install it locally

npm uninstall -g webpack
npm install --save-dev html-webpack-plugin webpack webpack-dev-server

You can link the global webpack pkg to your project's node modules. The downside of this is that your project will be forced to use most updated webpack. This will create a problem only when some updates are not backwards compatible.
```
npm i webpack -g; npm link webpack --save-dev
```

You can omit the html-webpack-plugin depending on your requirement.

You can find more info on this github issue page.

edited Mar 16, 2022 at 1:23

General Grievance

5,12039 gold badges40 silver badges60 bronze badges

answered Apr 4, 2017 at 8:20

Raunaqss

1,33713 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

Jonathan Corrin Over a year ago

Neither of those options worked for me. Just updated to npm 5+. I can build production locally but not while pushing to heroku. Keeps raising error but the module is definitely located in the correct place.

Raunaqss Over a year ago

@JonathanCorrin hmm that's unusual. NPM's cache gets confused sometimes, try clearing it using npm cache clean and then try installing webpack locally.

Raunaqss Over a year ago

Another thing I would try is to delete the node_modules directory and then do npm install again. This error occurs only when webpack doesn't exist locally, so if your package.json has webpack mentioned in its devDependencies—this should do the job.

Jonathan Corrin Over a year ago

For some reason none of those worked for me. I was able to get it to build but I'm unsure of what actually did the job. I removed node_modules && dist, cleaned the cache and downgraded webpack to 2.2.0. Its now building. I had tried removing node_modules and installing webpack locally to dev dependencies but it did not work yesterday.

prem30488 Over a year ago

This is very useful information and answer is perfect. Thank you.

|

Martin Brandl · Accepted Answer · 2022-04-29 08:25:56Z

36

I faced a similar issue when updating my Angular app using ncu. Finally solved it by:

remove the node_modules directory
remove package-lock.json
reinstall the packages.

You can run this in PowerShell (make sure you are in the correct working directory):

rm node_modules -r -force
rm package-lock.json
npm cache verify
npm install

edited Apr 29, 2022 at 8:25

answered Dec 27, 2017 at 21:37

Martin Brandl

59.4k16 gold badges151 silver badges190 bronze badges

Comments

Guillem Puche · Accepted Answer · 2021-04-25 09:57:42Z

10

Context:

I had this problem with a React application.

I tried to uninstall webpack globally and locally, also deleted the local folder node_modules, reinstalled all local npm modules (with npm install), etc.

Nothing worked, until doing this...

Solution:

Remove package-lock.json & node_modules.
Don't remove the other files (like: package.json, index.js...)
Install all package (npm extracts information for the installation from package.json) with npm install === npm i.
Now, run your code and voila! 🎉

edited Apr 25, 2021 at 9:57

answered Feb 28, 2019 at 20:10

Guillem Puche

1,44417 silver badges21 bronze badges

Comments

Shay · Accepted Answer · 2017-09-28 15:50:38Z

9

I tried for hours almost every thing suggested on different threads on Stack overflow but nothing worked. Eventually (with a lot of luck) I tried this and it worked:

deleted node_modules library (not sure if required)
npm install -g @angular/cli
npm install @angular/cli
npm install

answered Sep 28, 2017 at 15:50

Shay

4072 gold badges8 silver badges16 bronze badges

Comments

Audrey · Accepted Answer · 2021-04-08 14:51:43Z

7

This happened to me after I configed 'react-bootstrap' in my next js app. try adding this fixed my problem:

yarn add webpack@webpack-4

or if using npm:

npm i webpack@webpack-4

answered Apr 8, 2021 at 14:51

Audrey

4792 gold badges8 silver badges21 bronze badges

Comments

NVCoder · Accepted Answer · 2019-05-06 11:47:09Z

6

Below worked for me:-

Removed node_modules
Deleted package-lock.json
Run npm install

answered May 6, 2019 at 11:47

NVCoder

2113 silver badges5 bronze badges

Comments

imdzeeshan · Accepted Answer · 2019-02-02 11:29:06Z

0

Check webpack.config.js and make sure all dependencies are installed.

I was having the same problem too. It was resolved by installing html-webpack-plugin dependency. It was defined in my webpack.config.js but not installed.

answered Feb 2, 2019 at 11:29

imdzeeshan

1,12820 silver badges27 bronze badges

Comments

user3198259 · Accepted Answer · 2019-02-14 19:33:14Z

0

Remove the package-lock.json and try npm install it will resolve the issue.

answered Feb 14, 2019 at 19:33

user3198259

1941 gold badge3 silver badges13 bronze badges

Comments

MHS · Accepted Answer · 2021-01-06 13:23:43Z

0

This is work for me:

1. npm uninstall -g webpack
2. rm node_modules -r -force
3. rm package-lock.json
4. npm install

answered Jan 6, 2021 at 13:23

MHS

9491 gold badge14 silver badges32 bronze badges

Comments

0xcuonghx · Accepted Answer · 2021-04-02 01:46:38Z

0

You have to check webpack modules already install in the node_modules folder or on your machine? if not install it

answered Apr 2, 2021 at 1:46

0xcuonghx

6106 silver badges5 bronze badges

Comments

Arulkumar · Accepted Answer · 2021-05-10 13:59:12Z

0

For me I fixed this error with:

yarn add --save-dev webpack webpack-cli html-webpack-plugin webpack-dev-server webpack-dev-middleware

edited May 10, 2021 at 13:59

Arulkumar

13.3k14 gold badges51 silver badges76 bronze badges

answered May 10, 2021 at 13:15

EJA

453 bronze badges

Comments

unloco · Accepted Answer · 2021-06-14 20:49:02Z

0

It happened when I installed using yarn while the project used npm. I removed the node_modules folder then tried again with npm i

rm -rf node_module
npm install

The reason for this is that the project used specific packages versions which are compatible together but using yarn installed the newest versions which may not fully compatible with the current project.

Check which lock file the project uses then use the corresponding package manager.

answered Jun 14, 2021 at 20:49

unloco

7,3904 gold badges52 silver badges62 bronze badges

Comments

Tyler2P · Accepted Answer · 2022-03-20 17:25:21Z

0

This will fix your problem:

npm remove webpack -g
npm i webpack --save-dev

edited Mar 20, 2022 at 17:25

Tyler2P

2,37030 gold badges26 silver badges34 bronze badges

answered Mar 15, 2022 at 16:26

Ridvan Saman

111 bronze badge

2 Comments

General Grievance Over a year ago

"Remove global webpack and install it locally" --Top answer. Is this answer really unique?

arkon Over a year ago

Please see How to answer for details on how to provide quality answers. It's useful to provide context and details on why this might be an ideal solution.

Collectives™ on Stack Overflow

Error: Cannot find module 'webpack/lib/node/NodeTemplatePlugin'

13 Answers 13

Update (Apr 2018)

Older answer

8 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

13 Answers 13

Update (Apr 2018)

Older answer

8 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related