nodemon: Error: Cannot find module 'internal/util/types'
This is what I get when running nodemon with no arguments.
exception in nodemon killing node
Error: Cannot find module 'internal/util/types'
at Function.Module._resolveFilename (module.js:513:15)
at Function.Module._load (module.js:463:25)
at Module.require (module.js:556:17)
at require (internal/module.js:11:18)
at evalmachine.<anonymous>:31:26
at Object.<anonymous> (/usr/local/lib/node_modules/nodemon/node_modules/update-notifier/node_modules/configstore/node_modules/graceful-fs/fs.js:11:1)
at Module._compile (module.js:612:30)
at Object.Module._extensions..js (module.js:623:10)
at Module.load (module.js:531:32)
at tryModuleLoad (module.js:494:12)
I’m using node 8.8.1
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 23
- Comments: 63 (4 by maintainers)
Links to this issue
Commits related to this issue
- docs: update faq on issue #1124 — committed to remy/nodemon by remy 7 years ago
- try to fix the phantomjs error, it's Error: Cannot find module 'internal/util/types' https://github.com/remy/nodemon/issues/1124 .. maybe — committed to wiber/silver-bullet by wiber 5 years ago
I have solved it in this way:
i had this issue in my Win8.1 box; was going from
npm@3.10.3andnode@v6.4.0tonpm@5.5.1andnode@v8.9.3solved it by these steps: delete
C:\Users\<user>\AppData\Roaming\npm\node_modules\npmrunnpm install -g npmI think it is realated to: https://github.com/npm/npm/issues/19032 and it is closed. For me this helped.
On Windows, this is how it sorted out:
Go to <node dir>\global_modules\node_modules,
Delete the “npm” folder and all its contents,
Go to https://nodejs.org,
Download the “Recommended For Most Users” version (currently 8.9.1 LTS),
Install it
This worked for me on Win7.
I had this issue, I fixed it by dropping down my node version (to 6.2.2 in my case), updating npm, and then going back to Node v9.0.0.
I solved this by reinstalling bower. And running bower install
Using n for version management. What fixed it for me:
removing C:\Users{YOUR USERNAME}\AppData\Roaming\npm solve it for me
Ubuntu 17.04 Node v8.9.1
This was occurring to me when i tried to run my gulp scripts. I did few things, not really sure which one in particular solved it, but this is what i did:
Then i deleted my node_modules in my project and after the
npm ieverything worked.Okay, so what I did to fix my issue is, uninstalled my ionic-cli and installed the latest version. That fixed the issues. Do note that in latest version of ionic, commands execute with
ionic cordovainstead ofioniconly, with exception ofionic serve.I had the same issue. When i reverted to the older version of node js,the problem got solved.
I was able to solve this issue for me by deleting package-lock.json and rebuilding the node modules for my project.
For those who’re facing this issue on
ionicprojects after updating to Mac Sierra 10.13, know that the problem is with ionic CLI (v1.7.16). I was facing issue while creating builds using the normal ionic commandionic build androidand I was gettingThe solution is, instead of using ionic commands, use the
cordovacommands directly, like,cordova build androidHope that helps someone.Hello, why don’t you try:
Closing. This seems to be related to cached node_modules between version changes.
I fixed it like this (Windows): It turned out I had an old version of npm.exe in C:\ProgramData\chocolatey\bin Just run npm.exe install -g npm and it fixed it
On OSX High Sierra / Brew Installed, similar to @artemv and others:
on windows 7, i fixed the problem by going to C:\Users\my.username\AppData\Roaming\npm and deleting the node_modules folder. afterwards i could run “npm install” without problems.
using
node v9.8.0 npm v3.5.3
Having the same issue on windows 8.1 with node 8.9.1 and 9.2.0. Downgrading to node 6.12 solves the problem. Complete uninstall/installs don’t. How can possibly a stable node version be released like that?
Ah looks like node
v8.2.1works.I started to have this issue after another upgrade of Node (from 8.5.6 to 8.10.0 in my case) with
n. Following fixed it for me (needs yarn to be installed):@eternalsayed same problem here, same workaround!
Could you resolve how to do
ionic serve?@wema1043
node version : v8.9.0 npm : 5.5.1
After upgrade to OS X 10.13.1 it started failing.
brew upgrade node - fixed the issue