npm ERR! enoent and is related to npm not being able to find a file

15,085

According to the meanjs readme, node v5 is not supported yet. So you will probably need to downgrade to node v4 (LTS) or try your luck with the meanjs master branch and see if enough progress has been made yet to support node v5.

Share:
15,085
Mona Jalal
Author by

Mona Jalal

contact me at [email protected] I am a 5th-year computer science Ph.D. Candidate at Boston University advised by Professor Vijaya Kolachalama in computer vision as the area of study. Currently, I am working on my proposal exam and thesis on the use of efficient computer vision and deep learning for cancer detection in H&E stained digital pathology images.

Updated on June 04, 2022

Comments

  • Mona Jalal
    Mona Jalal almost 2 years

    How can I fix this? I also tried the master version and got a similar error. I am using OSX Yosemite:

    bash-3.2$ yo meanjs
    You're using the official MEAN.JS generator.
    ? What mean.js version would you like to generate? 0.4.0
    0.4.0
    ? In which folder would you like the project to be generated? This can be changed later. mean
    Cloning the MEAN repo.......
    ? What would you like to call your application? MEAN
    ? How would you describe your application? Full-Stack JavaScript with MongoDB, Express, AngularJS, and Node.js
    ? How would you describe your application in comma seperated key words? MongoDB, Express, AngularJS, Node.js
    ? What is your company/author name? University of Wisconsin-Madison/Mona Jalal
    ? Would you like to generate the article example CRUD module? Yes
    ? Would you like to generate the chat example module? Yes
    Running npm install for you....
    This may take a couple minutes.
    Error: Command failed: cd mean && npm install
    npm WARN deprecated [email protected]: Package renamed to phantomjs-prebuilt. Please update 'phantomjs' package references to 'phantomjs-prebuilt'
    npm WARN deprecated [email protected]: Grunt needs your help! See https://github.com/gruntjs/grunt/issues/1403.
    npm WARN deprecated [email protected]: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
    npm WARN deprecated [email protected]: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
    npm WARN deprecated [email protected]: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
    npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
    npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
    npm WARN prefer global [email protected] should be installed with -g
    npm WARN prefer global [email protected] should be installed with -g
    npm WARN prefer global [email protected] should be installed with -g
    npm WARN [email protected] requires a peer of kerberos@~0.0 but none was installed.
    npm ERR! Darwin 14.5.0
    npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
    npm ERR! node v5.8.0
    npm ERR! npm  v3.7.3
    npm ERR! path /Users/mona/interviews/mean/mean/node_modules/node-pre-gyp/bin/node-pre-gyp
    npm ERR! code ENOENT
    npm ERR! errno -2
    npm ERR! syscall chmod
    
    npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/mona/interviews/mean/mean/node_modules/node-pre-gyp/bin/node-pre-gyp'
    npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/mona/interviews/mean/mean/node_modules/node-pre-gyp/bin/node-pre-gyp'
    npm ERR! enoent This is most likely not a problem with npm itself
    npm ERR! enoent and is related to npm not being able to find a file.
    npm ERR! enoent 
    
    npm ERR! Please include the following file with any support request:
    npm ERR!     /Users/mona/interviews/mean/mean/npm-debug.log
    
        at ChildProcess.exithandler (child_process.js:202:12)
        at emitTwo (events.js:100:13)
        at ChildProcess.emit (events.js:185:7)
        at maybeClose (internal/child_process.js:850:16)
        at Socket.<anonymous> (internal/child_process.js:323:11)
        at emitOne (events.js:90:13)
        at Socket.emit (events.js:182:7)
        at Pipe._onclose (net.js:475:12)
    bash-3.2$