yeoman / generator-polymer

Scaffold out a Polymer project
http://polymer-project.org
926 stars 150 forks source link

Updated NPM - then Yeoman-Polymer; Now throwing bad error #114

Closed caseybaggz closed 9 years ago

caseybaggz commented 9 years ago

Just an FYI, I have reported this to npm/issues first - just wanted to give you a heads up of something crazy that went down. Just updated my NPM with npm updated -g and npm updated -g npm. Additionally, after that I updated all my yo-generators and they are all fine except the polymer one. :(

Getting this error preventing me from even using it:

Baggz-iMac:~$ yo
? 'Allo Casey! What would you like to do? Update your generators
? Generators to update: generator-polymer
npm WARN locking Error: EACCES, open '/Users/caseybaggz/.npm/_locks/generator-polymer-2ced2814dec48a08.lock'
npm WARN locking  /Users/caseybaggz/.npm/_locks/generator-polymer-2ced2814dec48a08.lock failed { [Error: EACCES, open '/Users/caseybaggz/.npm/_locks/generator-polymer-2ced2814dec48a08.lock']
npm WARN locking   errno: 3,
npm WARN locking   code: 'EACCES',
npm WARN locking   path: '/Users/caseybaggz/.npm/_locks/generator-polymer-2ced2814dec48a08.lock' }
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "generator-polymer"
npm ERR! node v0.10.31
npm ERR! npm  v2.1.12

npm ERR! Attempt to unlock /usr/local/lib/node_modules/generator-polymer, which hasn't been locked
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/caseybaggz/npm-debug.log

     _-----_
    |       |    .---------------------------------------.
    |--(o)--|    |        Bye from us! Chat soon.        |
   `---------´   |                                       |
    ( _´U`_ )    |            The Yeoman Team            |
    /___A___\    | https://github.com/yeoman/yeoman#team |
     |  ~  |     '---------------------------------------'
   __'.___.'__   
 ´   `  |° ´ Y ` 

events.js:74
        throw TypeError('Uncaught, unspecified "error" event.');
              ^
TypeError: Uncaught, unspecified "error" event.
    at TypeError (<anonymous>)
    at emit (events.js:74:15)
    at /usr/local/lib/node_modules/yo/yoyo.js:53:12
    at /usr/local/lib/node_modules/yo/node_modules/async/lib/async.js:254:17
    at done (/usr/local/lib/node_modules/yo/node_modules/async/lib/async.js:129:15)
    at /usr/local/lib/node_modules/yo/node_modules/async/lib/async.js:32:16
    at /usr/local/lib/node_modules/yo/node_modules/async/lib/async.js:251:21
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/yo/node_modules/async/lib/async.js:575:34)
    at ChildProcess.emit (events.js:98:17)
    at Process.ChildProcess._handle.onexit (child_process.js:810:12)

All the best.

caseybaggz commented 9 years ago

So the fix was to re-install npm & yeoman because npm update apparently does not do what you think it does...

Additionally, Yo only saves generators in the correct spot if I use a capital -G. Weird...

FIX #6924