-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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 './lib' #3606
Comments
Can you paste the entire stack trace? |
|
ref. npm/npm#10166 |
I think it probably has something to do with https://github.com/nodejs/node/blob/master/tools/osx-pkg.pmdoc/02npm.xml#L9 but I don't actually understand how OS X installers work. cc @othiym23 |
Hmmm, could 63a628d#diff-649abfdda4cfccbe318266e0c9116701L3 have been this issue? That commit was scheduled for v4.0.0 but doesn't seem to have landed until v5? |
+1 same os version and 5.0.0. |
On second look, that seems like just an identifier though... |
cc @nodejs/build for anyone who knows how the OS X installer works more |
@nicolabortignon ... I just want to be clear: you are not seeing this problem with |
@jasnell I did not have any issues with v4.2.1 From #npm irc:
|
@jasnell that is correct, 4.2.1 works like a charm. |
Ok cool. Taking it back off the lts-watch list then. |
Yep, as far as I can tell that one is not on the list. |
Actually.. wait... nevermind lol... I think it was just in the batch I just did lol (double checking to make sure it's not... getting conflicting information) ... Update: Ok, nevermind, we're good. I hadn't pushed that set of changes yet, it was just in a local test branch. We're good 👍 |
Failed on OS X for me. Not able to install any packages. Works on 4.2. |
cc @nodejs/build or @nodejs/collaborators does anyone know enough about the OS X installer to somehow make https://github.com/nodejs/node/blob/master/tools/osx-pkg.pmdoc/02npm.xml remove the previous version properly? i.e. origin commit: 63a628d#diff-649abfdda4cfccbe318266e0c9116701L3 (Rolling back this commit will only make matters worse at this point.) |
|
@Fishrock123 OSX installers are a bit of a joke, I suspect the best you can do is run a custom perl script during the installation to do a cleanup. There's no real concept of an "uninstaller" for OSX which I find baffling. Perhaps the best way to tackle this is to look at #2571 because we're ditching the old packager anyway and this new tool might have an easier option for cleanup. |
I had this issue earlier today and I fixed it by removing npm ( |
rm'ing it worked for me as well, but I thought maybe I was having problems because at one time i installed it with brew, and maybe even ports too.. either way, rm all them and installing stable worked for me. thanks! |
Installing newer Node updates worked without issue. Perhaps it only occurs when going from |
WORKS! Thanks @stevenvachon |
Without cached node modules huh? I'll investigate more ~Monday. |
Is this still an issue? |
@jasnell Unless the installer has been updated to remove |
@iarna there is a PR open to change the installer (for osx at least) --> #5656 It includes a commit to remove npm during install --> eff981b I had done some work in a branch to try and getting a script working to do this with the current installer but couldn't get it working. I plan to dig into it again, but it might not be a good use of time if the other PR is ready to land |
... yep. |
plz fix my bug as soon as possible |
@amodkumar57 your problems look unrelated to this issue, which is about npm not working. Can you post over at https://github.com/nodejs/help with more information about the problem you are having |
I don't have a node_modules folder in
|
Same issue when I run phonegap run ios Output :
|
had this exact issue on Ubuntu bash in windows. Deleting the given folder worked perfect. |
how to do centos |
This issue has been inactive for sufficiently long that it seems like perhaps it should be closed. Feel free to re-open (or leave a comment requesting that it be re-opened) if you disagree. I'm just tidying up and not acting on a super-strong opinion or anything like that. |
|
Just installed node v5 and running
npm
in command line produces said error.OS X 10.10.5
How to Fix
(For now)
(Edited in by @Fishrock123)
The text was updated successfully, but these errors were encountered: