Error Cannot find module webpack

Question

I m just getting started with webpack and am having difficulty getting the multiple-entry-points sample to build   The webpack config js file in the example includes the line   var CommonsChunkPlugin   require        lib optimize CommonsChunkPlugin      which fails for me with the error  Error  Cannot find module        lib optimize CommonsChunkPlugin    Searching around  I found other examples of using the CommonsChunkPlugin with the expression  var commonsPlugin   new webpack optimize CommonsChunkPlugin  common js      which fails with the error  ReferenceError  webpack is not defined   Some more searching found a number of examples including  var webpack   require  webpack      and my build now fails with   Error  Cannot find module  webpack    I m at a loss as to how to proceed

User · Answer

for me  it is a wrong error feedback   there was config error in webpack config js    delete the file and start over solved my issue

User · Answer

Open npm command prompt and -- cd solution folder  and then  just run npm link webpack in NPM cmd prommt and re build

User · Answer

Run below commands in Terminal   npm install --save-dev webpack  npm install --save-dev webpack-dev-server

User · Answer

Seems to be a common Windows problem  This fixed it for me   Nodejs cannot find installed module on Windows    Add an environment variable called NODE PATH and set it to  USERPROFILE  Application Data npm node modules  Windows XP    AppData  npm node modules  Windows 7   or wherever npm ends up installing the modules on your Windows flavor  To be done with it once and for all  add this as a System variable in the Advanced tab of the System Properties dialog  run control exe sysdm cpl System 3     Note that you can t actually use another environment variable within the value of NODE PATH  That is  don t just copy and paste that string above  but set it to an actual resolved path like C  Users MYNAME AppData Roaming npm node modules

User · Answer

I was having this issue on OS X and it seemed to be caused by a version mismatch between my globally installed webpack and my locally installed webpack-dev-server  Updating both to the latest version got rid of the issue

User · Answer

You can try this   npm install --only dev   It works for me

User · Answer

Just found out that using Atom IDE terminal did not install dependencies locally  probably a bug or just me   Installing git bash externally and running npm commands again worked for me

User · Answer

While working on windows  I ve installed webpack locally and it fixed my problem  So  on your command prompt  go to the directory of which you want to run webpack  install webpack locally  without the -g  and enjoy

User · Answer

I solved the same problem by reinstalling  execute these commands  rm -Rf node modules rm -f package-lock json npm install   rmis always a dangerous command  especially with -f  please notice that before executing it

User · Answer

Nothing suggested above worked for me  including the NODE PATH variable   I created a sym link of  node modules  from my local folder to the global AppData eg below  and it worked like charm   C  Users mmoinuddin AppData Roaming npm gt mklink  D node modules c  essportreact day1 node modules symbolic link created for node modules  lt  lt     gt  gt  c  essportreact day1 node modules C  essportreact day1 gt webpack Hash  2a82a67f90f9aa05ab4a Version  webpack 1 15 0

User · Answer

npm link webpack worked for me   My webpack configuration       webpack     4 41 2        webpack-dev-server     3 9 0        webpack-cli     3 3 10

User · Answer

If you have installed a node package and are still getting message that the package is undefined  you might have an issue with the PATH linking to the binary   Just to clarify a binary and executable essentially do the same thing  which is to execute a package or application  ei webpack     executes the node package webpack  In both Windows and Linux there is a global binary folder   In Windows I believe it s something like C   Windows System32 and in Linux it s usr bin   When you open the terminal command prompt  the profile of it links the PATH variable to the global bin folder so you are able to execute packages applications from it  My best guess is that installing webpack globally may not have successfully put the executable file in the global binary folder   Without the executable there  you will get an error message   It could be another issue  but it is safe to say the that if you are here reading this  running webpack globally is not working for you  My resolution to this problem is to do away with running webpack globally and link the PATH to the node module binary folder  which is  node modules  bin  WINDOWS  add node modules  bin to your PATH  Here is a tutorial on how to change the PATH variable in windows  LINUX  Go to your project root and execute this    export PATH  PWD node modules  bin  PATH   In Linux you will have to execute this command every time you open your terminal   This link here shows you how to make a change to your PATH variable permanent

User · Answer

Installing both webpack and CLI globally worked for me   npm i -g webpack webpack-cli

User · Answer

Link globally installed package to your project  npm link webpack

User · Answer

I had a ton of issues getting a very simple  NET Core 2 0 application to build in VS 2017  This is the error from AppVeyor  however it was essentially the same thing locally    some paths omitted for security        Performing first-run Webpack build         module js 327      throw err       EXEC   error   Cannot find module           node modules webpack bin webpack js       at Function Module  resolveFilename  module js 325 15       at Function Module  load  module js 276 25       at Function Module runMain  module js 441 10       at startup  node js 140 18       at node js 1043 3      csproj 25 5   error MSB3073  The command  node node modules webpack bin webpack js --config webpack config vendor js  exited with code 1       Build FAILED    I stumbled upon this question and answer  and I noticed my local instance also had the same warning sign over the  Project Root  - gt  Dependencies - gt  npm folder  Right clicking and hitting  Restore packages  got everything loaded up properly  and I was able to build successfully

User · Answer

For Visual Studio users  Right click on the npm folder and  quot Restore Packages quot

User · Answer

On windows  I have observed that this issue shows up if you do not have administrative rights  i e   you are not a local administrator  on the machine   As someone else suggested  the solution seems to be to install locally by not using the -g hint

[node.js] Error: Cannot find module 'webpack'

Examples related to node.js

Examples related to webpack