[Bug]: Cannot find module 'webpack' #299

jesperlandmer · 2018-03-01T12:02:50Z

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Whenever I try to run webpack, I get this error message:

`vagrant@vagrant-ubuntu-trusty-32:/vagrant$ webpack
/usr/lib/node_modules/webpack-cli/bin/webpack.js:237
                                throw err;
                                ^

Error: Cannot find module 'webpack'
    at Function.Module._resolveFilename (module.js:538:15)
    at Function.Module._load (module.js:468:25)
    at Module.require (module.js:587:17)
    at require (/usr/lib/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at Object.<anonymous> (/vagrant/webpack.config.tsx:1:77)
    at Module._compile (/usr/lib/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Module.require (module.js:587:17)
    at require (/usr/lib/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at WEBPACK_OPTIONS (/usr/lib/node_modules/webpack-cli/bin/convert-argv.js:133:13)
    at requireConfig (/usr/lib/node_modules/webpack-cli/bin/convert-argv.js:135:6)
    at /usr/lib/node_modules/webpack-cli/bin/convert-argv.js:142:17
    at Array.forEach (<anonymous>)
    at module.exports (/usr/lib/node_modules/webpack-cli/bin/convert-argv.js:140:15)
    at yargs.parse (/usr/lib/node_modules/webpack-cli/bin/webpack.js:234:39)
    at Object.parse (/usr/lib/node_modules/webpack-cli/node_modules/yargs/yargs.js:539:18)
    at /usr/lib/node_modules/webpack-cli/bin/webpack.js:212:8
    at Object.<anonymous> (/usr/lib/node_modules/webpack-cli/bin/webpack.js:504:3)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Module.require (module.js:587:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/lib/node_modules/webpack/bin/webpack.js:12:2)
    at Module._compile (module.js:643:30)

If the current behavior is a bug, please provide the steps to reproduce.
I'm using Vagrant, and just installed webpack and webpack cli globally.
Using:

node.js: v8.9.4
npm: v5.6.0
webpack: v4.0.1
webpack-cli: v2.0.9

What is the expected behavior?
To bundle the files

Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language.
I'm using Typescript and React on a Node machine. Vagrant runs on Ubuntu

The text was updated successfully, but these errors were encountered:

ghost · 2018-03-01T13:02:32Z

I have a similar problem:

TypeError: Cannot read property 'presetToOptions' of undefined

Described by someone else on StackOverflow

evenstensberg · 2018-03-01T14:19:18Z

@andriibyk-apiko what version are you on?

ghost · 2018-03-01T14:21:27Z

@ev1stensberg

"webpack": "^4.0.1",
"webpack-cli": "^2.0.9"

evenstensberg · 2018-03-01T14:51:14Z

Mind printing your prefix paths?

evenstensberg · 2018-03-01T14:51:57Z

Could you do a console log before the error throws on webpack?

jesperlandmer · 2018-03-01T16:40:26Z

Also had the same problem with "presetToOptions" as @andriibyk-apiko, but then I reinstalled webpack and then I got this error instead. Installed Webpack v.^2.0.0 instead and now it works.

Don't know what prefix paths is

evenstensberg · 2018-03-01T20:27:48Z

npm config get prefix

ghost · 2018-03-02T07:23:10Z

Mind printing your prefix paths?

/usr

ashclarke · 2018-03-02T12:30:01Z

Mind printing your prefix paths?

C:\Users\<user>\AppData\Roaming\npm

[email protected] (global)
[email protected] (local)

Stacktrace:

C:\Users\<user>\AppData\Roaming\npm\node_modules\webpack-cli\bin\webpack.js:237
                            throw err;
Error: Cannot find module 'webpack'
    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 (C:\Users\<user>\AppData\Roaming\npm\node_modules\webpack-cli\node_modules\v8-compile-cache\v8-compile-cache.js:159:20)
    at Object.<anonymous> (C:\Users\<user>\AppData\Roaming\npm\node_modules\webpack-cli\bin\convert-argv.js:7:42)
    at Module._compile (C:\Users\<user>\AppData\Roaming\npm\node_modules\webpack-cli\node_modules\v8-compile-cache\v8-compile-cache.js:178:30)
    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 yargs.parse.err (C:\Users\<user>\AppData\Roaming\npm\node_modules\webpack-cli\bin\webpack.js:234:14)
    at Object.parse (C:\Users\<user>\AppData\Roaming\npm\node_modules\webpack-cli\node_modules\yargs\yargs.js:539:18)
    at C:\Users\<user>\AppData\Roaming\npm\node_modules\webpack-cli\bin\webpack.js:212:8
    at Object.<anonymous> (C:\Users\<user>\AppData\Roaming\npm\node_modules\webpack-cli\bin\webpack.js:504:3)
    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> (C:\<source-path>\node_modules\webpack\bin\webpack.js:12:2)
    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.runMain (module.js:604:10)

evenstensberg · 2018-03-02T13:36:46Z

This might be hard for me to reproduce, anyone from @webpack/core-team that can?

ashclarke · 2018-03-02T14:46:42Z

@ev1stensberg - Not sure it helps, but it seems to only affect the global install.

I installed webpack-cli locally and it works, but you get the "prefer global" warning.

imjar · 2018-03-05T10:49:20Z

use
$ webpack-cli init

evenstensberg · 2018-03-05T11:04:10Z

@ashclarke that might be cause our prefer to global is wrong ( I think ), will investigate.

dhruvdutt · 2018-03-11T19:16:50Z

@jesperlandmer @ashclarke Can you output npm root -g?

Related PR #332.

ashclarke · 2018-03-12T16:32:27Z

@dhruvdutt - C:\Users\<user>\AppData\Roaming\npm\node_modules

evenstensberg · 2018-03-12T19:24:57Z

Can you try updating?

quantuminformation · 2018-03-20T19:55:05Z

Not sure if this is related, but if you run npm i here https://github.com/quantumjs/solar-popup/tree/master/demo

Then run webpack-cli I get

                                throw err;
                                ^

Error: Cannot find module 'webpack'

Webpack was running as normal when using webpack 3

dhruvdutt · 2018-03-20T20:15:14Z

@quantuminformation You missed installing webpack-cli. Just do npm i -D webpack-cli inside your demo dir and you're set. 💯

quantuminformation · 2018-03-20T20:53:06Z

Many thanks for this!

ematipico · 2018-03-20T22:04:42Z

Is this issue still valid?

evenstensberg · 2018-03-21T07:39:52Z

Friendly ping @jesperlandmer

jesperlandmer · 2018-03-21T08:17:37Z

Don’t know! I think the main issue has to do with Vagrant and how Vagrant handles global values. I had several problems with other dependencies as well (e.g. Firebase). Staying with docker from now on

evenstensberg · 2018-03-21T08:22:56Z

Okay. Let's keep this open for others to come to if they have similar issues!

okonet · 2018-03-28T10:29:58Z

Same issue with the global install.

npm install -g webpack-cli and running webpack-cli throws:

•100% ➜ webpack-cli
/usr/local/lib/node_modules/webpack-cli/bin/webpack.js:242
				throw err;
				^

Error: Cannot find module 'webpack'
    at Function.Module._resolveFilename (module.js:543:15)
    at Function.Module._load (module.js:470:25)
    at Module.require (module.js:593:17)
    at require (/usr/local/lib/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at Object.<anonymous> (/usr/local/lib/node_modules/webpack-cli/bin/convert-argv.js:7:24)
    at Module._compile (/usr/local/lib/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Module.require (module.js:593:17)
    at require (internal/module.js:11:18)
    at yargs.parse (/usr/local/lib/node_modules/webpack-cli/bin/webpack.js:239:14)
    at Object.parse (/usr/local/lib/node_modules/webpack-cli/node_modules/yargs/yargs.js:543:18)
    at /usr/local/lib/node_modules/webpack-cli/bin/webpack.js:217:8
    at Object.<anonymous> (/usr/local/lib/node_modules/webpack-cli/bin/webpack.js:512:3)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Function.Module.runMain (module.js:690:10)
    at startup (bootstrap_node.js:194:16)
    at bootstrap_node.js:666:3

nebrelbug · 2018-08-29T13:28:11Z

@ev1stensberg any updates? Installing webpack and webpack-cli locally doesn't work for me, and neither does npx webpack or running webpack-cli, and I tried rm -rf node_modules and then reinstall. Until then, what should I do?

nebrelbug · 2018-08-29T13:49:27Z

I uninstalled globally webpack and webpack-cli and then reinstalled, and it seems to be working so far...

evenstensberg · 2018-08-29T17:03:57Z

Working on fixing this but haven’t had a lot of spare time lately. Sorry for the inconviniences.. 👨🏼‍🔧

nebrelbug · 2018-08-29T17:50:52Z

@ev1stensberg in the meantime, what should I do to follow best practices with my projects?

evenstensberg · 2018-08-29T18:15:04Z

Anything that runs webpack is viable. Ideal case is to run it through node modules by installing them both locally as devDeps. If that doesn’t work, then look in the issue thread 🤗

twentytwokhz · 2018-10-11T09:41:22Z

@quantuminformation You missed installing webpack-cli. Just do npm i -D webpack-cli inside your demo dir and you're set. 💯

Many thanks, it worked!

TENsaga · 2018-10-11T22:29:38Z

OP appears to be using Unix, but I had the same error after multiple project restarts/npm installs. For those using WSL / Bash for Windows I noticed sometimes npm install fails to install some of the binaries. Webpack and webpack-dev-server were missing in my case.

ls node_modules/.bin/  

// if the binaries are missing run any combo of:
npm i -D webpack webpack-cli webpack-dev-server 

// we had to modify our package.json to access the binary with the full path (instead of just npx webpack):
build:dev: "npx ./node_modules/.bin/webpack --config ./webpack.config/service.dev.js --watch",

Spent half a day trying to figure this out and ran through most of the suggestions here, hopefully it helps someone.

hazone · 2018-10-18T13:01:21Z

I only got it to work by first install npm install -g webpack-cli and then npm install -g webpack.

yvonnendutaw · 2018-11-14T09:46:10Z

I only got it to work by first install npm install -g webpack-cli and then npm install -g webpack.

Thanks! This worked for me too!

gogromat · 2018-11-14T19:57:35Z

Note: installing webpack globally is not recommended.
For now I reference it as node_modules/webpack/bin/webpack.js in package.json/scripts section

mosesnova · 2018-11-16T21:50:01Z

npm i -D webpack-cli Worked for me.

Jacknq · 2018-12-11T19:11:08Z

Same issue, deleting node_modules and package-lock then npm install - worked for me

thnx to th3n3wguy and similar issue
Cannot find module 'webpack/lib/RequestShortener' vuejs/vue-cli#2548 (comment)

TCarmine · 2019-01-13T10:31:54Z

I only got it to work by first install npm install -g webpack-cli and then npm install -g webpack.

This worked for me in the way that it then did found finally the webpack-cli module but then I got this warnings and error:

WARNING in configuration
The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment.
You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/concepts/mode/

ERROR in multi ./app.js bundle.js
Module not found: Error: Can't resolve 'bundle.js' in '/home/carmine/Desktop/JS/webpack_app'
@ multi ./app.js bundle.js main[1]

TCarmine · 2019-01-13T11:07:45Z

I solved my last issue thanks to this : https://stackoverflow.com/questions/49389677/module-not-found-error-cant-resolve-bundle-js-in-users-jonathankuhl-docum

dupls · 2019-03-06T21:37:20Z

You can try running webpack directly from the node_modules folder, this seems to solve a lot of the red errors in the terminal.

./node_modules/.bin/webpack

And if you don't want to keep typing that line you can add a build script in your package.json file
"scripts": { "build": "./node_modules/.bin/webpack" ...
Then in the terminal you can just type
npm run build

willdonner · 2019-03-14T03:23:50Z

npm link webpack
npm link webpack-cli
https://stackoverflow.com/questions/29492240/error-cannot-find-module-webpack
Worked for me.

cabello · 2019-05-28T14:24:39Z

I likely cannot provide much insight but this was affecting me not locally on macOS but on my continuous integration provider linux/Ubuntu, after debugging with SSH in the CI, I found out that webpack-cli 3.2.0 was the first version to introduce this issue, so I downgraded it to 3.1.2 in my package.json:

- "webpack-cli": "3.2.0",
+ "webpack-cli": "3.1.2",

And it worked! I also tried many webpack 4.X and they all seemed to work with cli 3.1.2.

CI debugging data:

Docker Engine Version: 18.09.1
Kernel Version: Linux 31e94c1fa4b9 4.15.0-1035-aws #37-Ubuntu SMP Mon Mar 18 16:15:14 UTC 2019 x86_64 Linux
Starting container node:10.12.0

evenstensberg · 2019-05-29T07:57:44Z

Have you tried updating to the latest CLI version? Is the issue still persistent?

cabello · 2019-05-29T11:55:15Z

Yes, i also tried the latest version, forgot to mention it.

…

On Wed, May 29, 2019, 3:57 AM Even Stensberg ***@***.***> wrote: Have you tried updating to the latest CLI version? Is the issue still persistent? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#299?email_source=notifications&email_token=AAAO4CGJVB5TJRDYZYTXUXLPXYZPXA5CNFSM4ETAZQV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWOP67A#issuecomment-496828284>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAO4CESOUDV7BYUQ54REHDPXYZPXANCNFSM4ETAZQVQ> .

evenstensberg · 2019-05-29T23:06:37Z

Alright. Aware this is a bug, but the bug is due the fact that you have a global and a local installation or vice versa. Could you try aligning CLI installation location with webpack location?

heldrida · 2019-06-26T13:32:57Z

Hey, got a new machine and I don't have webpack and webpack-cli installed globally; Debugging at the moment but seems that the reports above are correct, the bug still persists; I'll update the comment with more info after I fully understand what's going on.

The following is for a project that has a dependecy

devDependecies: {
    "foobar": "git+https://gitlab+deploy-token-1:xxxxx@yyyyyy/foobar.git#vTag",
}


{ Error: Cannot find module 'webpack-cli'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at runCommand.then (/Users/punkbit/www/temp1/node_modules/webpack/bin/webpack.js:142:5)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7) code: 'MODULE_NOT_FOUND' }

these are all the globals I have installed in the machine

npm list -g --depth 0:

├── [email protected]
└── [email protected]

Decided to cd into node_modules/foobar and tried:

npx webpack -v

One CLI for webpack must be installed. These are recommended choices, delivered as separate packages:
 - webpack-cli (https://github.com/webpack/webpack-cli)
   The original webpack full-featured CLI.
We will use "npm" to install the CLI via "npm install -D".
Do you want to install 'webpack-cli' (yes/no):

During npm install outside the node_modules/foobar I do get "One CLI for webpack must be installed...", which I accept but in the end there's the error I've reported earlier or at the top Error: Cannot find module 'webpack-cli'

which webpack
webpack not found

Fixed after:

testing local version through npm link
moved webpack, wepback-cli to dependencies not devDependencies
found a package that failed on import, during build command where env set to production, moved to dependencies not devDependencies
cleared cache --force and retested to make sure

tkdphoenix · 2019-07-03T23:29:35Z

#299 (comment)
This worked for me. Once I ran npm link on webpack and webpack-cli it worked after that. No need to not follow best practice and install globally.

monu2580 · 2019-11-28T05:51:46Z

i was getting the same error " [Bug]: Cannot find module 'webpack' "
i fixed this Error after following these steps:
Step-1: Run this command to install webpack

 npm install --save-dev webpack webpack-cli

Step-2: uninstall Webpack

 npm uninstall --save-dev webpack webpack-cli

step-3: Delete node-module folder from your project directory

 rm -rf node_modules

step-4: Run npm install

 npm install

step-5: Run yarn command

 yarn

step-6: Run start command

yarn  start

or

npm start

This is working for me

monu2580 · 2019-11-28T06:04:24Z

halcwb · 2020-08-23T20:11:27Z

So, I tried about everthing in this thread:

uninstalled the global webpack, using only local install
updated to the latest versions
linked webpack and webpack-cli

No luck!! Only directly running with node node_modules/webpack-dev-server/bin/webpack-dev-server.js works.

Maybe a bug with > 91 comments is an indication??

alexander-akait · 2020-11-05T14:03:22Z

Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks!

If somebody faced with the problem again please open the new issue with reproducible example, I think we fixed it (please use webpack-cli@4)

isaldarriaga · 2021-02-11T00:34:42Z

i was able to solve this problem in fedora 33 this way:

install nvm
nvm install 10.23.3 # node version!
cd <your node path>
rm -Rf node_modules/
gedit package.json
Add "webpack": "^4.39.3" to "devDependencies"
npm install
npm start

jesperlandmer changed the title ~~Can't find webpack~~ Cannot find module 'webpack' Mar 1, 2018

evenstensberg added the Bug label Mar 1, 2018

evenstensberg mentioned this issue Mar 10, 2018

Global webpack-cli should work without webpack installed #236

Closed

evenstensberg added question Chill ❄️ and removed Bug labels Mar 21, 2018

evenstensberg changed the title ~~Bug: Cannot find module 'webpack'~~ [Bug]: Cannot find module 'webpack' Oct 31, 2019

halcwb mentioned this issue Aug 23, 2020

Straight out of the box template failure SAFE-Stack/SAFE-template#388

Closed

alexander-akait closed this as completed Nov 5, 2020

[Bug]: Cannot find module 'webpack' #299

[Bug]: Cannot find module 'webpack' #299

Comments

jesperlandmer commented Mar 1, 2018 • edited Loading

ghost commented Mar 1, 2018

evenstensberg commented Mar 1, 2018

ghost commented Mar 1, 2018

evenstensberg commented Mar 1, 2018

evenstensberg commented Mar 1, 2018

jesperlandmer commented Mar 1, 2018 • edited Loading

evenstensberg commented Mar 1, 2018

ghost commented Mar 2, 2018

ashclarke commented Mar 2, 2018 • edited Loading

evenstensberg commented Mar 2, 2018

ashclarke commented Mar 2, 2018

imjar commented Mar 5, 2018

evenstensberg commented Mar 5, 2018

dhruvdutt commented Mar 11, 2018

ashclarke commented Mar 12, 2018

evenstensberg commented Mar 12, 2018

quantuminformation commented Mar 20, 2018 • edited Loading

dhruvdutt commented Mar 20, 2018

quantuminformation commented Mar 20, 2018

ematipico commented Mar 20, 2018 • edited Loading

evenstensberg commented Mar 21, 2018

jesperlandmer commented Mar 21, 2018

evenstensberg commented Mar 21, 2018

okonet commented Mar 28, 2018

nebrelbug commented Aug 29, 2018 • edited Loading

nebrelbug commented Aug 29, 2018

evenstensberg commented Aug 29, 2018

nebrelbug commented Aug 29, 2018

evenstensberg commented Aug 29, 2018

twentytwokhz commented Oct 11, 2018

TENsaga commented Oct 11, 2018 • edited Loading

hazone commented Oct 18, 2018

yvonnendutaw commented Nov 14, 2018

gogromat commented Nov 14, 2018

mosesnova commented Nov 16, 2018

Jacknq commented Dec 11, 2018 • edited Loading

TCarmine commented Jan 13, 2019

TCarmine commented Jan 13, 2019

dupls commented Mar 6, 2019 • edited Loading

willdonner commented Mar 14, 2019 • edited Loading

cabello commented May 28, 2019

evenstensberg commented May 29, 2019

cabello commented May 29, 2019 via email

evenstensberg commented May 29, 2019

heldrida commented Jun 26, 2019 • edited Loading

tkdphoenix commented Jul 3, 2019

monu2580 commented Nov 28, 2019

monu2580 commented Nov 28, 2019

halcwb commented Aug 23, 2020

alexander-akait commented Nov 5, 2020

isaldarriaga commented Feb 11, 2021

jesperlandmer commented Mar 1, 2018 •

edited

Loading

jesperlandmer commented Mar 1, 2018 •

edited

Loading

ashclarke commented Mar 2, 2018 •

edited

Loading

quantuminformation commented Mar 20, 2018 •

edited

Loading

ematipico commented Mar 20, 2018 •

edited

Loading

nebrelbug commented Aug 29, 2018 •

edited

Loading

TENsaga commented Oct 11, 2018 •

edited

Loading

Jacknq commented Dec 11, 2018 •

edited

Loading

dupls commented Mar 6, 2019 •

edited

Loading

willdonner commented Mar 14, 2019 •

edited

Loading

heldrida commented Jun 26, 2019 •

edited

Loading