Ошибка cannot find module

After pulling down a module from GitHub and following the instructions to build it, I try pulling it into an existing project using:

> npm install ../faye

This appears to do the trick:

> 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:

> 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.<anonymous> (/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?

asked Jan 26, 2012 at 18:57

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.

answered Jan 26, 2012 at 19:15

BillBill

24.8k7 gold badges94 silver badges124 bronze badges

I had a very similar issue. Removing the entire node_modules folder and re-installing worked for me:

rm -rf node_modules
npm install

answered May 25, 2015 at 10:30

Abhinav SinghAbhinav Singh

7,7621 gold badge22 silver badges33 bronze badges

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.

bruntime

3712 silver badges13 bronze badges

answered Jun 17, 2015 at 8:51

Piyush ChordiaPiyush Chordia

1,2851 gold badge9 silver badges7 bronze badges

rm package-lock.json
rm -r node_modules
npm i

That should fix issue and install all packages.

answered Mar 26, 2021 at 11:53

XakiruXakiru

2,4481 gold badge14 silver badges11 bronze badges

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.

answered Oct 3, 2017 at 9:12

mgthomas99mgthomas99

4,9003 gold badges18 silver badges21 bronze badges

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.

answered Aug 6, 2015 at 16:23

Alex WernerAlex Werner

3603 silver badges9 bronze badges

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

answered Feb 6, 2018 at 3:34

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.

answered Aug 25, 2016 at 8:37

ukosteopathukosteopath

4236 silver badges14 bronze badges

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.

answered Jun 10, 2016 at 11:30

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.

answered Jun 23, 2017 at 14:30

MrCrankyMrCranky

1,47824 silver badges31 bronze badges

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

answered Aug 10, 2020 at 17:07

james acejames ace

2,25224 silver badges15 bronze badges

Remove your node_module root folder from your project(eg: myApp).
Go to myApp folder and then type below command from terminal

>myApp>npm install

It will install all the dependency modules required for your project.

answered Jul 6, 2016 at 7:25

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!

answered Sep 6, 2016 at 9:35

DaveDave

2,97334 silver badges32 bronze badges

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.

answered Sep 6, 2017 at 5:20

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!

answered May 18, 2017 at 20:17

Yevgeny SimkinYevgeny Simkin

27.7k39 gold badges136 silver badges234 bronze badges

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.

answered Jul 10, 2017 at 5:57

martinp999martinp999

3995 silver badges9 bronze badges

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

answered Dec 20, 2019 at 6:22

Kartik GarasiaKartik Garasia

1,2241 gold badge17 silver badges25 bronze badges

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

answered Oct 18, 2017 at 11:50

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:

«scripts»: {
…
«server»: «live-server public —host=localhost —port=3000 —middleware=./disable-browser-cache.js»
…
}
«scripts»: {
To:

…
«server»: «live-server public —host=localhost —port=3000 —middleware=../../disable-browser-cache.js»
…
}

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:

"live-server": "https://github.com/tapio/live-server/tarball/master"

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.

answered Dec 21, 2020 at 20:42

JGFMKJGFMK

8,1354 gold badges53 silver badges92 bronze badges

In my case,

npm install -D tslib @types/node

solved my problem, I was then able to run

ts-node index.ts

successfully.

answered Jul 7, 2021 at 15:58

xpagesbeastxpagesbeast

7661 gold badge8 silver badges21 bronze badges

Run the following commands step by step. It fixed my issue:

npm cache clean –force
rm package-lock.json
rm -r node_modules
npm i —save —legacy-peer-deps

answered Sep 21, 2022 at 10:09

YasirYasir

3993 silver badges10 bronze badges

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 <= 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!

answered Apr 6, 2016 at 7:53

BelgorBelgor

1811 gold badge2 silver badges9 bronze badges

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.

answered Apr 19, 2017 at 0:22

ChrisChris

2,7561 gold badge29 silver badges34 bronze badges

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')

answered Feb 3, 2018 at 17:14

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/

answered Apr 12, 2019 at 15:50

KalKal

1813 silver badges15 bronze badges

In my case, i was not using the proper version of nvm.

answered Jul 28, 2021 at 5:51

maverickmaverick

821 silver badge14 bronze badges

A rare but also possible case is a typo in the module name. I missed the «s» in the file name when executing node .util.js, where it should be node.utils.js and didn’t find any solution among all the answers under this question until I found out that I can’t run the file even if I delete everything!

answered Sep 4, 2021 at 12:31

skygateskygate

3712 silver badges11 bronze badges

Apparently, judging by this question, there are a LOT of possible causes.

Maybe this will help someone, hoping nobody was as stupid as I was to use this technique:

Check if you have any node_modules folder up the folder tree.

Scenario 1:
If you ever had a projects folder, where you shared a node_modules folder between multiple projects, you may not have had any problems

|- projects
| |- node_modules     <- OK
| |- project1         <- No node_modules folder
| | |- package.json
| |- project2         <- No node_modules folder
| | |- package.json

Scenario 2:
If you add a third project of a different nature, you may choose to keep a node_modules folder in that project:

|- projects
| |- node_modules     <- Can be used by project 3
| |- project1         <- No node_modules folder
| | |- package.json
| |- project2         <- No node_modules folder
| | |- package.json
| |- project3
| | |- node_modules   <- Packages for project 3 only
| | |- package.json

I’m guessing some packages in project 3’s node-modules folder are relying on packages that it finds (or doesn’t find) in the parent folder’s node_modules folder. Even though you’d expect the dependencies to be found in project 3’s node_modules folder. Maybe it’s because of the way some packages are imported and referenced?

Goes without saying that’s a disaster waiting to happen

answered Feb 16, 2022 at 19:14

DerpyNerdDerpyNerd

4,6786 gold badges39 silver badges90 bronze badges

I ran into this issue when I was upgrading the node version along with installing several different package versions. The project created a docker image/container to work in.

The issue was that the Docker image wasn’t recreated when I added a package and rebuilt the project. The proper information had been in my local package.json and package-lock.json files.

Deleting the Docker image and not just the container solved my problem.

answered Apr 29, 2022 at 14:11

majestzimmajestzim

5186 silver badges16 bronze badges

what ended up working for me was making sure to include any merge-deep dependencies as an external in your webpack config:

externals: {
    puppeteer: 'require("puppeteer")',
}

And to declare the node_modules path relative to your package.json in your package.json as an ‘extraResource’.

"extraResources": [
    "node_modules/puppeteer,
}

answered Dec 13, 2022 at 14:37

Источник

If you’re a developer that works with Node JS and JavaScript libraries and frameworks like React, Vue, and Angular, then you might have encountered the «Error: cannot find module» error.

In this article, I’m going to show you how to fix the error.

Why the «Error: cannot find module» Occurs

This error occurs because of the following reasons:

you’re trying to import an item from a module you don’t have installed in your project directory
you’re importing some things from an outdated package
you’re pointing to a file that does not exist

In the screenshot below, you can see that I’m getting the error:

ss1

I’m getting the error because I’m trying to import the freeCodeCamp icon from the react-icons package, which I don’t have installed.

import { FaFreeCodeCamp } from "react-icons/fa";

How to Fix the «cannot find module» Error

If you get this error, the solution is always in the error. The module (package) not found is always specified in the format «Module not found: Error: Can’t resolve ‘package name’ in ‘project directory».

In my case, I got it like this «Module not found: Error: Can’t resolve ‘react-icons/fa’ in ‘C:UsersuserDesktopProjectsAddress Locatoraddress-locatorsrc'».

To fix the error, you need to install the package that is absent in your project directory – npm install package-name or yarn add package-name.

In my case, I need to install the react-icons package so the freeCodeCamp icon can be resolved. I’ll do that by running yarn add react-icons.

Once I install the package and run the app, everything should successfully compile:

ss2

If you install the package but you still get the error, then follow the steps below:

delete the node modules folder by running rm -rf node_modules
delete package.lock.json file by running rm -f package-lock.json
clean up the NPM cache by running npm cache clean --force
install all packages again by running npm install

That should fix the error for you.

Conclusion

When you get the “cannot find module” error, or “module not found”, it means you’ve not installed the package you’re trying to use.

If the error occurs even if you have the package installed, then the fixes suggested in this article can help you out.

Thank you for reading.

Learn to code for free. freeCodeCamp’s open source curriculum has helped more than 40,000 people get jobs as developers. Get started

Источник

When you are working in Node, you will sometimes encounter the error Cannot find module 'module-name' with the error code MODULE_NOT_FOUND.

The error looks like this:

	internal/modules/cjs/loader.js:796
    throw err;
    ^

Error: Cannot find module 'module'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:793:17)
    at Function.Module._load (internal/modules/cjs/loader.js:686:27)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
    at internal/main/run_main_module.js:17:11 {
        code: 'MODULE_NOT_FOUND',
        requireStack: []
    }

In this post, we’ll learn how to resolve this error.

What is the problem?

The issue is that Node is unable to find the module that you are trying to import into your Node application.

The most common reason for this is that you simply haven’t installed the project’s dependencies yet.

The project’s dependencies are listed in the package.json file at the root of the project.

The Solution

To fix the Cannot find module error, simply install the missing modules using npm.

To so, you can use the following command:

	npm install

If you are using the yarn package manager, you can use the following command:

	yarn install

This will install the project’s dependencies into your project so that you can use them.

Sometimes, this might still not resolve it for you. In this case, you’ll want to just delete your node_modules folder and lock file (package-lock.json or yarn.lock) and try again.

This is how you can delete the node_modules folder and lock files:

	rm -rf node_modules

rm package-lock.json
rm yarn.lock

Local files

If your module is not coming from a remote source, you are seeing the error because the path to the local file is not correct.

Try to confirm that the path pointing to the local module is correct and your error should be resolved.

Conclusion

The Cannot find module error is a common error that usually happens when dependencies are not installed. Once you install your dependencies and ensure that the paths are correct, you can resolve the error and run your application successfully.

Hopefully, this resolved the issue for you.

Thanks for reading!

If you want to learn about web development, founding a start-up, bootstrapping a SaaS, and more, follow me on Twitter! You can also join the conversation over at our official Discord!

Support Us
Join
Share
Tweet
Share

Give feedback on this page!

Источник

JavaScript’s Node.js server supports module export and import in both ECMAScript modules and CommonJS format.

Sometimes, npm will throw an error saying Cannot find module because of module import as shown below:

$ node index.js
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'axios'
Require stack:
- /n-app/index.js
    at ... {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/n-app/index.js' ]
}

Here’s the content of the index.js file:

var axios = require("axios");

The cannot find module error occurs because npm cannot find the module required by the index.js file. In this case, the axios module.

To resolve the error, you need to make sure that axios is installed in the node_modules/ folder.

Please note that the node_modules/ folder must be located in the same directory as the index.js file:

.
├── index.js
├── node_modules
├── package-lock.json
└── package.json

If you have run the npm install command before, then it’s possible that the installation of the module is incomplete or corrupted.

Delete the node_modules/ folder using the rm -rf node_modules command, then run npm install again. That may fix the issue.

Finally, the same error can happen when you require() a local .js file that can’t be found.

Suppose you have a file named lib.js placed in the same folder as the index.js file:

.
├── index.js
└── lib.js

To import the file, you need to specify the correct path in the require() function.

The following code:

var helper = require("lib.js");

Will produce the same error:

$ node index.js
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'lib.js'
Require stack:
- /n-app/index.js
    at ... {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/n-app/index.js' ]
}

This is because the require() function will always look inside the node_modules/ folder.

To let Node.js knows that you are importing a local file, use the absolute path as follows:

The ./ syntax means the root directory where you run the node command. In this case, the folder where index.js is located.

If you have a file one level down like this:

.
├── index.js
└── helpers
    └── lib.js

Then you need to adjust the require() path as shown below:

var helper = require("./helpers/lib.js");

The same also applies when you use the ES modules format as follows:

import helper from "./helpers/lib.mjs";

To conclude, the error “Cannot find module” happens when Node.js can’t find the module that a file is trying to import.

You can see the file and the module that’s causing the issue from the error output generated by Node itself.

And that’s how you resolve the npm cannot find module issue. Great work! 😉

Источник

Why we get “Error: Cannot find module”?

Working with Node can be a bit frustrating when dealing with error messages especially ones that have to deal with modules. Error: Cannot find module 'package-name' is a popular module error message that you might face when working with Node and its packages which comes most likely because of missing module which is required by the application.

In this article, we will discuss how to deal with handling this error message.

Solution: Install missing module using Node Package Manager

The Node Package Manager, popularly known as npm is a command line tool that helps us to install, update or manage Node.js packages. So, if you can’t find a module, npm is our go-to guy to deal with this issue.

Method-1: npm install

The first approach is to check if we have the module or package at first or install the module directly. The command to perform this operation can be seen below.

npm install package-name

If the package-name is not installed, the output could look like this

7 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

However, if you have it installed, it could look like this. Emphasis on the up to date.

up to date, audited 58 packages in 1s

7 packages are looking for funding
  run `npm fund` for details

If you are trying to install a module that you created yourself or pulled from GitHub, you can go to root directory of the folder holding the package.json file and execute the above command or the below

npm install ../package-name

or simply, the npm install command, which accesses the package.json file to see the modules needed.

ALSO READ: 4 different ways to read JSON file in NodeJS

Method-2: npm install -g

If the above section doesn’t work to solve the Error: Cannot find module 'package-name' error message, you could try to install it globally. This allows us to use the module from any directory. To achieve this, we need to add the -g flag to the npm command.

npm install -g express

There is a possibility that you are access the module from a directory that doesn’t have access to that module, and therefore, if you install globally, you can access the package.

Method-3: npm ci

Also, if the repository or project you are working with uses the package-lock.json, you have to use another command other than npm install.

The npm command appropriate for such scenarios can be seen below

npm ci

Summary

Depending on the issue at hand, any of the above section could be useful to solve your Error: Cannot find module 'package-name' error message. You can try out all of these approaches if you don’t know for sure what’s going on. However, it is important to know what each command does which has been explained.

Why the «Error: cannot find module» Occurs

How to Fix the «cannot find module» Error

Conclusion

What is the problem?

The Solution

Local files

Conclusion

Why we get “Error: Cannot find module”?

Solution: Install missing module using Node Package Manager

Method-1: npm install

Method-2: npm install -g

Method-3: npm ci

Summary

Further Readings

Читайте также: