npm start no longer works after node upgrade

[wwsean08]

After upgrading npm as well as node via nvm I am no longer able to run kibana using npm start from the source root. As you can see the output I have node 4.2.4 being used as well as npm 2.14.15 in use. I checked the npm-debug log and there was no extra info in there but will attach it if needed.

This is on the master branch with no changes.

[ssmith@localhost config]$ npm -v
2.14.15
[ssmith@localhost config]$ npm install
[ssmith@localhost config]$ nvm list
       v0.10.41
        v0.12.7
        v0.12.9
    iojs-v3.3.1
->       v4.2.4
         system
node -> stable (-> v4.2.4) (default)
stable -> 4.2 (-> v4.2.4) (default)
niojs -> iojs-v3.3 (-> iojs-v3.3.1) (default)
[ssmith@localhost config]$ npm start

> [email protected] start /home/ssmith/kibana
> ./bin/kibana --dev

 watching for changes  (90 files)
server    log   [21:11:48.941] [info][optimize] Waiting for optimizer completion
optmzr    log   [21:11:49.100] [info][optimize] Lazy optimization of bundles for kibana and statusPage ready
optmzr    log   [21:11:49.133] [fatal] SyntaxError: Cannot parse records: Unexpected end of input
    at Object.parse (native)
    at Compiler.<anonymous> (/home/ssmith/kibana/node_modules/webpack/lib/Compiler.js:313:25)
    at Storage.finished (/home/ssmith/kibana/node_modules/webpack/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:38:16)
    at /home/ssmith/kibana/node_modules/webpack/node_modules/enhanced-resolve/node_modules/graceful-fs/graceful-fs.js:76:16
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
 optimizer crashed  with status code 1

npm ERR! Linux 3.10.0-327.4.4.el7.x86_64
npm ERR! argv "/home/ssmith/.nvm/versions/node/v4.2.4/bin/node" "/home/ssmith/.nvm/versions/node/v4.2.4/bin/npm" "start"
npm ERR! node v4.2.4
npm ERR! npm  v2.14.15
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `./bin/kibana --dev`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script './bin/kibana --dev'.
npm ERR! This is most likely a problem with the kibana package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ./bin/kibana --dev
npm ERR! You can get their info via:
npm ERR!     npm owner ls kibana
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ssmith/kibana/config/npm-debug.log

[spalger]

@wwsean08 that error happens sometimes, and is usually caused by the process getting killed in a strange way. You should be able to nuke the /optimize directory at the root of the source and things should work.

[Osezno]

Hey i have this same problem what should i do?

[wwsean08]

Blowing out the contents of the optimize directory (minus the hidden file) fixed it for me @Osezno