How do I resolve Cannot find module error using Node js

Question

After pulling down a module from GitHub and following the instructions to build it  I try pulling it into an existing project using    gt  npm install    faye   This appears to do the trick    gt  npm list  home dave src server  -- faye 0 7 1    -- cookiejar 1 3 0    -- hiredis 0 1 13    -- redis 0 7 1   But Node js can t find the module    gt  node app js node js 201         throw e     process nextTick error  or  error  event on first tick                 Error  Cannot find module  faye      at Function  resolveFilename  module js 334 11      at Function  load  module js 279 25      at Module require  module js 357 17      at require  module js 368 17      at Object  lt anonymous gt    home dave src server app js 2 12      at Module  compile  module js 432 26      at Object  js  module js 450 10      at Module load  module js 351 31      at Function  load  module js 310 12      at Array 0  module js 470 10    I really want to understand what is going on here  but I m at a bit of a loss as to where to look next  Any suggestions

User · Answer

This happens when a first npm install has crashed for some reason (SIGINT of npm), or that the delay was too long, or data is corrupted. Trying an npm install again won't save the problem.

Something got wrong on the npm first check, so the best choice is to remove the file and to restart npm install.

User · Answer

Specify the path to the restler folder  which will be inside node modules folder like   var rest   require    node modules restler     This worked for me

User · Answer

Encountered this problem while using webpack with webpack-dev-middleware   Had turned a single file into a folder   The watcher seemed to not see the new folder and the module was now missing   Fixed by restarting the process

User · Answer

In my case I had UNMET PEER DEPENDENCY  redux  3 0 0 causing this error message  see all of them and install missing modules again using --save  npm install redux --save

User · Answer

I had a very similar issue  Removing the entire node modules folder and re-installing worked for me   rm -rf node modules npm install

User · Answer

Removing node npm and then re-installing the stable not the latest  version worked for me   sudo rm -rf  usr local  lib node    npm  modules  bin share man   npm  node  man1 node    https   nodejs org en download

User · Answer

I experienced this error yesterday  Took me a while to realise that the main entry in package json was pointing to a file that I d moved  Once I updated that the error disappeared and the package worked

User · Answer

If all other methods are not working for you    Try npm link package name  e g npm link webpack npm link autoprefixer  e t c

User · Answer

PRO TIP   This error happened to me  while fighting fatigue and mild illness  because I typed node blah instead of npm blah   The error message received wasn t angry enough to alert me to my own folly

User · Answer

I can add one more place to check  the package that I was trying to use was another one of my own packages that I had published to a private NPM repo   I had forgotten to configure the  main  property in the package json properly   So  the package was there in the node modules folder of the consuming package  but I was getting  cannot find module    Took me a few minutes to realise my blunder   -

User · Answer

For TypeScript users  if you are importing a built-in Node module  such as http  path or url  and you are getting an error such as  Cannot find module  x  then the error can be fixed by running  npm install  types node --save-dev   The command will import the NodeJS TypeScript definitions into your project  allowing you to use Node s built-in modules

User · Answer

I faced the same problem when someone else in the team updated package json in SVN  Merely removing the node modules directory did not help   How I solved the problem is   rm -rf node modules rm package json rm package-lock json svn up npm install ng build --env prod   Hope this helps someone

User · Answer

Using npm install installs the module into the current directory only  in a subdirectory called node modules    Is app js located under home dave src server    If not and you want to use the module from any directory  you need to install it globally using npm install -g   I usually install most packages locally so that they get checked in along with my project code   Update  8 2019    Nowadays you can use package-lock json file  which is automatically generated when npm modifies your node modules directory  Therefore you can leave out checking in packages  because the package-lock json tracks the exact versions of your node modules  you re currently using  To install packages from package-lock json instead of package json use the command npm ci   Update  3 2016    I ve received a lot of flak for my response  specifically that I check in the packages that my code depends on   A few days ago  somebody unpublished all of their packages  https   kodfabrik com journal i-ve-just-liberated-my-modules  which broke React  Babel  and just about everything else   Hopefully it s clear now that if you have production code  you can t rely on NPM actually maintaining your dependencies for you

User · Answer

I had this issue using live-server  using the Fullstack React book   I kept getting   Error  Cannot find module    disable-browser-cache js         I had to tweak my package json  From   quot scripts quot          quot server quot    quot live-server public --host localhost --port 3000 --middleware   disable-browser-cache js quot         quot scripts quot      To       quot server quot    quot live-server public --host localhost --port 3000 --middleware       disable-browser-cache js quot          Notice relative paths seem broken awkward       becomes        I found the issue here Also if anyone follows along with that book   change devDependencies in packages json to     quot live-server quot    quot https   github com tapio live-server tarball master quot    Currently that upgrades from v1 2 0 to v1 2 1  It s good to use nvm  It s best to install v13 14 of Node   v14  creates other headaches  nvm install v13 14 0 nvm alias default v13 14 0 Update npm with npm i -g npm 7 3 0 run  npm update you can use npm list to see the hierarchy of dependencies too   For some reason node 15   latest npm defaults to only showing first level of depth - a la package json  That renders default command pointless  You can append --depth n  to make command more useful again   you can use npm audit too  There issues requiring  update of chokidar and some others packages  to newer versions  live-server hasn t been updated to support the newer corresponding node v 14 library versions   See similar post here  Footnote  Another thing when you get to the JSX section  check out my answer here  https   stackoverflow com a 65430910 495157 When you get to   Advanced Component Configuration with props  state  and children  P182   node version 13 isn t supported for some of the dependencies there  Will add findings for that later too

User · Answer

Check if the enviroment variable NODE PATH is set correctly and pointing to the node modules path  nodejs uses this variable to search for the libraries

User · Answer

First of all  yes  a part of my answer definitely is helpful to solve the error that is posted by OP  Secondly  after trying the below step  I faced a couple of other errors  and so  have written the solution of those too    Psst  I am not sure if I ve successfully helped in solving the above error  or if I ve broken some rule or format of answering  but I faced the above error and some others and it took much time for me to find the proper solutions for those errors  I m writing the complete solution because in case  if someone else also faces these errors  then he ll hopefully get a solution here    So adding to  and elaborating the answer provided by PrashanthiDevi  and also adding my personal experience  here it is   I am new to the whole e2e and unit tests part  I started looking into this part from Protractor  Now I already had the files in which tests were written  but I had to run the tests   I had already installed all the required softwares and tools  but when I initially ran the code for running the tests  gulp itest  I got this  Cannot find module  Error  After going through many different questions on SO  I found one answer that I thought could help getting a solution   The person had suggested to run the command npm install in my project folder   The reason for doing this was to update the node-modules folder  inside our project folder  with all the required and necessary files and dependencies    The below part maybe irrelevant with this question  but might be helpful if anyone came across the same situation that I faced    The above step surely solved my previous error  but threw a new one  This time the error being Could not find chromedriver at     node modules protractor selenium chromedriver      However  the solution of this error was pretty silly  and funny  to me  I already had the chromedriver file in my selenium folder  But  turns out that the above error was coming because my chromedriver files were inside selenium folder and not inside chromedriver folder  So  creating a chromedriver folder and copying the chromedriver files there solved my problem   Also  for the error  Timed out waiting for the WebDriver Server  you could add this line of code to conf js file inside exports config      seleniumAddress   http   localhost 8080    Hope this helps

User · Answer

Just found an unusual scenario that may be of use to someone and is sort of a red herring   I was also getting the Cannot Find Module error but oddly everything worked perfectly in my local  Mac hosted  Node js environment  This problem only appeared when the code was deployed on our Linux server   Well    it turned out to be a typo that  apparently  the Mac based Node js installation was perfectly happy to ignore   The include looked like this   var S3Uploader   require    S3Uploader class      But the actual file was called  s3Uploader class js   Notice the casing difference in the  s  vs   S  between the code and the filename   So - in the odd chance that none of the other solutions here are solving your problem  triple check that you re not mis-casing the characters in your included filename      and DUH

User · Answer

I was trying to publish my own package and then include it in another project  I had that issue because of how I ve built the first module  Im using ES2015 export to create the module  e g lets say the module looks like that   export default function who    world        return  Hello   who        After compiled with Babel and before been published    use strict    Object defineProperty exports     esModule         value  true      exports default   function          var who   arguments length  lt   0    arguments 0      undefined    world    arguments 0         return  Hello     who       So after npm install module-name in another project  none ES2015  i had to do  var hello   require  module-name   default   To actually got the package imported   Hope that helps

User · Answer

Change the directory and point to your current project folder and then  npm install      This will install all dependencies and modules into your project folder

User · Answer

npm install --save module name   For example  if the error is         Error  Cannot find module   root  npm form-data   code   MODULE NOT FOUND       then you can resolve this issue by executing the command npm install --save form-data

User · Answer

If you are using typescript and getting an error after installing all node modules then remove package-lock json  And then run npm install

User · Answer

This error can be encountered if you are requireing a module that has a missing or incorrect main field in its package json  Though the module itself is installed  npm node has to use a single  js file as an entrypoint to your module  If the main field is not there  it defaults to looking for index js in your module s folder  If your module s main file is not called index js  it won t be able to require it   Discovered while turning a browserify-based module into a CommonJS require-able module  browserify didn t care about the missing main field  and so the error had gone unnoticed

User · Answer

Remove your node module root folder from your project eg  myApp   Go to myApp folder and then type below command from terminal   gt myApp gt npm install   It will install all the dependency modules required for your project

User · Answer

If you use nvm  check that existing node modules that are bindings to other libraries are compiled for the correct Node js version   I was having the same error  The reason was the following  We use nvm since we re running two apps on a server  one requires Node js 5 6 because it uses node-gd  which doesn t run on Node js 6 for now   the other requires Node js 6  Node js 6 is the apt-get installation   Also we use the pm2 tool to deploy   So  the default setup is that the pm2 process starts when nvm is not in effect  so it uses the apt-get installation of Node js  version 6   So the main pm2 daemon starts with Node js 6  If I run applications in fork mode they start in separate processes and nvm settings are in effect  When I run applications in cluster mode - they inherit the non-nvm environment   So when I tried to switch to the cluster mode the application failed to start because the bindings compiled for 5 6 fail with this message   I ve fixed that by restarting pm2 when nvm setings are in effect  Also startup scripts should be fixed

User · Answer

Maybe like me you set  view engine  in express to an engine that doesn t exist  or tried to use an unregistered templating engine  Make sure that you use   app engine  engine name  engine  app set  view engine   engine name

User · Answer

Please install the new CLI v3  npm install -g ionic latest     If this issue is still a problem in CLI v3  Thank you

[node.js] How do I resolve "Cannot find module" error using Node.js?

Examples related to node.js