Cannot find module '***' [Windows]
See original GitHub issue- Version: 19.16.0
- Target: windows 7 x64
Im building an app on windows. When build success and run app , then got error "Cannot find module “ultron”.
If add “ultron” to dependencies, got an other error : "Cannot find module “safe-buffer”.
I know issuse 217 but cannot work for me . module.paths is undifined
?
Anyone have ideas…
You see, if build on mac, more modules did put in than build on windows in win-unpacked\resources\app\node_modules
folder
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
node.js - Nodejs cannot find installed module on Windows
The answer for windows 10 is to set the NODE_PATH in the enviroment variables with C:\Users\User\node_modules. Share.
Read more >Error: Cannot find module 'node-windows' #57 - GitHub
This sounds like a path problem with your node/npm install. All reactions.
Read more >Error Nodejs cannot find installed module on Windows
I am learning nodejs at the moment on Windows. Several modules are installed globally with npm.cmd, and nodejs failed to find the installed ......
Read more >cannot find module [Node npm Error Solved] - freeCodeCamp
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....
Read more >Cannot find module 'X' error in Node.js | bobbyhadz
To solve the "Cannot find module" error in Node.js, make sure to install the package from the error message if it's a third-party...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@develar Aha thanks… Its work for me now. FUCK NPM
As far I see (in my case solution “remove package-lock.json” helps), DO NOT USE F**** NPM. Sorry for capslock, but please do not ever use npm and never store
package-lock.json
(if you use npm by error, remove created package-lock.json after it and use only yarn).