1.2.1 update fails.

[JeremyLC]

Atom 1.7.0
Windows 10 Professional, 1511 Build 10586
I also experienced the same failure on Windows Server 2012 R2.

1.1.2 worked fine, but the 1.2.1 update fails to install with the following output:

Updating to “[email protected]” failed.Hide output…

> [email protected] install C:\Users\JCRABT~1\AppData\Local\Temp\3\apm-install-dir-116314-4588-ud2phr\node_modules\tablr\node_modules\pathwatcher\node_modules\runas
> node-gyp rebuild


C:\Users\JCRABT~1\AppData\Local\Temp\3\apm-install-dir-116314-4588-ud2phr\node_modules\tablr\node_modules\pathwatcher\node_modules\runas>if not defined npm_config_node_gyp (node "C:\Users\jcrabtree\AppData\Local\atom\app-1.6.2\resources\app\apm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node  rebuild ) 

gypnpm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\\Users\\jcrabtree\\AppData\\Local\\atom\\app-1.6.2\\resources\\app\\apm\\bin\\node.exe" "C:\\Users\\jcrabtree\\AppData\\Local\\atom\\app-1.6.2\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\jcrabtree\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\jcrabtree\\.atom\\.apmrc" "install" "C:\\Users\\JCRABT~1\\AppData\\Local\\Temp\\3\\d-116314-4588-1rj9gzq\\package.tgz" "--target=0.34.5" "--arch=ia32"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

[benbalter]

Getting a similar failure on OS X.

[abe33]

Hi there, sorry for the inconvenience, I was waiting for Atom to ship pathwatcher in version 6.5 but it still stuck to 6.2 (it's the package that provide the file model used in Atom, and latest version includes a stream API) so I included the module directly in tablr. I guess I'll have to include the stream method in tablr directly to avoid having runas as a deep dependency.