Error: Cannot find module '/opt/node-0.10.16/lib/node_modules/npm/lib/build.js' #3812

Closed
binarykitchen opened this Issue Aug 21, 2013 · 7 comments

Comments

Projects
None yet
4 participants
@binarykitchen

Each time I run a sudo npm update -g I get this. But the file build.js is there.

> node -v && npm -v
v0.10.16
1.3.8

Can anyone explain?

@dharmavagabond

This comment has been minimized.

Show comment
Hide comment
@dharmavagabond

dharmavagabond Aug 22, 2013

Try npm cache clean. It worked for me.

Try npm cache clean. It worked for me.

@binarykitchen

This comment has been minimized.

Show comment
Hide comment
@binarykitchen

binarykitchen Aug 23, 2013

How is the cache related to this? Does not make sense to me ...

How is the cache related to this? Does not make sense to me ...

@dharmavagabond

This comment has been minimized.

Show comment
Hide comment
@dharmavagabond

dharmavagabond Aug 23, 2013

I’m sorry mate; I don’t know why clearing the cache made npm update -g work again.

I’m sorry mate; I don’t know why clearing the cache made npm update -g work again.

@binarykitchen

This comment has been minimized.

Show comment
Hide comment
@binarykitchen

binarykitchen Aug 23, 2013

OK. Can anybody explain? And why does the cache not clear / invalidate itself after certain operations?

OK. Can anybody explain? And why does the cache not clear / invalidate itself after certain operations?

@luk-

This comment has been minimized.

Show comment
Hide comment
@luk-

luk- Aug 23, 2013

Contributor

When the cache is told to be cleared, it is cleared.

On Thursday, August 22, 2013, Michael Heuberger wrote:

OK. Can anybody explain? And why does the cache not clear / invalidate
itself after certain operations?


Reply to this email directly or view it on GitHubhttps://github.com/isaacs/npm/issues/3812#issuecomment-23144275
.

Contributor

luk- commented Aug 23, 2013

When the cache is told to be cleared, it is cleared.

On Thursday, August 22, 2013, Michael Heuberger wrote:

OK. Can anybody explain? And why does the cache not clear / invalidate
itself after certain operations?


Reply to this email directly or view it on GitHubhttps://github.com/isaacs/npm/issues/3812#issuecomment-23144275
.

@timoxley

This comment has been minimized.

Show comment
Hide comment
@timoxley

timoxley Jan 8, 2014

Member

@binarykitchen Sometimes (rarely) the cache does get confused and needs to be cleared. Are you still having this issue? Can please try using the latest version of npm (currently 1.3.23) and close this if your specific issue is resolved?

#4430

Member

timoxley commented Jan 8, 2014

@binarykitchen Sometimes (rarely) the cache does get confused and needs to be cleared. Are you still having this issue? Can please try using the latest version of npm (currently 1.3.23) and close this if your specific issue is resolved?

#4430

@binarykitchen

This comment has been minimized.

Show comment
Hide comment
@binarykitchen

binarykitchen Jan 8, 2014

For reasons I cannot explain nor elaborate, I am not having this issue anymore. Closing now.

For reasons I cannot explain nor elaborate, I am not having this issue anymore. Closing now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment