Skip to content
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

Undeclared dependency on "clone" causes npm install to fail #1871

Closed
lox opened this issue Feb 25, 2015 · 5 comments
Closed

Undeclared dependency on "clone" causes npm install to fail #1871

lox opened this issue Feb 25, 2015 · 5 comments

Comments

@lox
Copy link

lox commented Feb 25, 2015

On installing semantic-ui, I get the following error:

|
> [email protected] install /Users/lachlan/.go/src/github.com/lox/xyz/node_modules/semantic-ui
> gulp install

module.js:338
    throw err;
          ^
Error: Cannot find module 'clone'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/lachlan/.go/src/github.com/lox/xyz/node_modules/gulp-util/node_modules/vinyl/index.js:2:13)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
@jlukic
Copy link
Member

jlukic commented Feb 25, 2015

Just tested on ubuntu with npm install semantic-ui and its working for me. If you have a package.json setup for your project try rming node_modules and re-installing with npm update

If you are still getting the issue, do you have any more info. Do you have other dependencies in the project? What platform?

@jlukic
Copy link
Member

jlukic commented Feb 27, 2015

Perhaps try npm cache clean

@jlukic jlukic closed this as completed Mar 12, 2015
@dannynimmo
Copy link

@lox Did you ever work out what was happening? I'm getting this same error.

@manuphatak
Copy link

@dannynimmo I got this after keyboard interrupting a package installation. npm cache clean and reinstalling said package did the job.

@italomaia
Copy link

I'm having this issue on ubuntu 17.04

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

No branches or pull requests

5 participants