-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Cannot find module 'internal/util/types' #1124
Comments
Ah looks like node |
I had the same issue. When i reverted to the older version of node js,the problem got solved. |
Still happening in v8.9.0. npm ERR! Cannot find module 'internal/util/types' Although nodejs seemed to install without errors. |
I've dropped down to v8.2.1 and still hit the same issues:
|
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'm using nvm I'm wondering if I need to clear out remove something after dropping down the versions of node to then run the npm update. I've tried just dropping and running the update but I still get the same error. |
I found the cause of the problem.This problem occurs if the default path of the command line is set in the registry again |
How do you fix that? 😂
I'm using ubuntu fwiw
…On Thu, 9 Nov 2017, 08:07 ifredom, ***@***.***> wrote:
I found the cause of the problem.This problem occurs if the default path
of the command line is set in the registry again
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1124 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABXXNFH2xvmsCGSeWjZ-asdA5ndnQe1Vks5s0rLNgaJpZM4QLuLN>
.
|
I fixed it like this (Windows): |
Same for v8.9.1, when trying to install angular CLI: D:\playground\ng>npm install -g @angular/cli@latest npm ERR! Cannot find module 'internal/util/types' npm ERR! Please include the following file with any support request: |
I think it is realated to: |
On Windows, this is how it sorted out:
This worked for me on Win7. |
Anyone have instructions for Ubuntu. I would assume same deal remove node
modules and start over?👊👍
…On Sun, 12 Nov 2017, 17:22 aromot, ***@***.***> wrote:
On Windows, this is how it sorted out:
1.
Go to \global_modules\node_modules,
2.
Delete the "npm" folder and all its contents,
3.
Go to https://nodejs.org,
4.
Download the "Recommended For Most Users" version (currently 8.9.1
LTS),
5.
Install it
This worked for me on Win7.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1124 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABXXNP9XRxVSsmFaapv8aZ4kTUeRBsg5ks5s1ylegaJpZM4QLuLN>
.
|
After upgrade to OS X 10.13.1 it started failing. brew upgrade node - fixed the issue |
I am having the same issue on Mac. My tests are failing. Error: Cannot find module 'internal/util/types' node version : v8.9.1 Any help would be appreciated. |
@mmilenkovic I'm running OS X 10.13.1 and node 8.9.1 but still having this issue |
node version : v8.9.0 |
got it with Node v6.2.2 |
I solved it by reinstalling nodejs. |
I have solved it in this way:
|
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? |
I solved this by reinstalling bower. And running bower install |
Closing. This seems to be related to cached node_modules between version changes. |
For those who're facing this issue on
The solution is, instead of using ionic commands, use the |
@eternalsayed same problem here, same workaround! Could you resolve how to do |
I'm using
|
@eternalsayed didn't work for me (in High Sierra), same output:
|
It was working for me because I hadn't stopped my |
Okay, so what I did to fix my issue is, uninstalled my ionic-cli and installed the latest version. That fixed the issues.
|
https://github.com/remy/nodemon/blob/master/faq.md#error-cannot-find-module-internalutiltypes this isn't a nodemon issue, it's npm, but others have had success with that faq item. |
I had this issue,I fixed it by dropped down my node version to 6.12.0 |
removing C:\Users{YOUR USERNAME}\AppData\Roaming\npm |
I found that I can use npm version 9.0.0 but I had to uninstall gulp-sass and then reinstall it. All was fine after that |
On Ubuntu, if you've installed your own copy of node you'll need to clean everything up. So remove node and npm. Then get rid of the node_modules directory... in my case
For others use find or locate to discover where your node_modules directories may be:
I also removed my .npm directory in my home dir: Note, it may be suitable to just remove the npm subdirectories from node_modules directories above, but I did not test this. I just went for clean then I reinstalled the same version of node that was giving me the problems. In my case that was 8.9.4LTS, with the normal |
I started to have this issue after another upgrade of Node (from 8.5.6 to 8.10.0 in my case) with
|
on windows 7, i fixed the problem by going to using node v9.8.0 |
Hello, why don't you try:
|
On OSX High Sierra / Brew Installed, similar to @artemv and others:
|
maybe you have multiple versions graceful-fs
|
I was running into this too with Ionic, and tried all of the remedies above and nothing worked. Then, just to see what would happen, I ran Ionic CLI 2.2.1 |
Ve a tu carperta node_modules |
I had the same issue. I was using node 8.11.0. Now I have downgraded it to 6.0.0 and it will work. Thanks for your valuable suggestions |
For my Mac, I had to remove node/npm/npm settings/reinstall node LTS/Cordova -- only 1 sudo command should be required. remove node and global node_modules
remove npm user settings from your profile
install NVM
install Node LTS with NVM
update ionic project by removing any previous node_modules, reinstall ionic/cordova
finally, add iOS platform works...
All of this setup my Mac with the following versions:
|
I had the same issue with Node 10.3.0 (Windows 10). I followed the instructions for handling a similar error here and it fixed both errors. The command was: |
Had this issue using Win 10 Wsl, node v. 9.3.0, npm v. 6.1.0 & gulp 3.9 and what helped using gulp again was |
Using n for version management. What fixed it for me:
|
…nal/util/types' remy/nodemon#1124 .. maybe
@aromot where can i find \global_modules\node_modules ? |
@QuocCong after removing i /c/Users/JoSuper/AppData/Roaming/npm/ get this $ cordova platform add android@6 |
@josuper The "global_modules" folder is located at the root of your NodeJS installation. I can't tell where it is exactly, I'm using a custom folder instead of the default path proposed by the installation. |
Downgrading the node version worked for me. I used volta-cli to try a few different node versions until I found one that works. |
C:\xampp\htdocs\DICA\dica-upload-ok-calendario-ko>npm run dev
internal/modules/cjs/loader.js:638 Error: Cannot find module 'internal/util/types' npm ERR! A complete log of this run can be found in: C:\xampp\htdocs\DICA\dica-upload-ok-calendario-ko>yarn install Can someone help me? |
Upgrading the node version to the stable one worked for me. |
I know it's closed but i want to add a alternative solution for this problem. Yes, node version update works every time. Because it's related with npm package version. Real problem is npm version to old for this. You can update npm version with node version. For example: nodejs.org download page said that: "Latest LTS Version: 12.14.1 (includes npm 6.13.4)". If you uninstall npm in your global and after that install again, you will fix this issue. |
This is what I get when running
nodemon
with no arguments.I'm using node 8.8.1
The text was updated successfully, but these errors were encountered: