search

ricardofbarros / linter-js-standard

Atom linter plugin for JavaScript, using JavaScript Standard Style
https://atom.io/packages/linter-js-standard
MIT License
99 stars 48 forks source link

Problems installing/updating package #108

Closed jagged3dge closed 8 years ago

jagged3dge commented 8 years ago

Trying to install linter-js-standard@3.3.1 on my Windows 7 Ultimate Edition box...

Installing “linter-js-standard@3.3.1” failed.Hide output…

> spawn-sync@1.0.15 postinstall C:\Users\Gary\AppData\Local\Temp\apm-install-dir-116319-5660-kskuc1\node_modules\linter-js-standard\node_modules\standard\node_modules\standard-format\node_modules\esformatter\node_modules\npm-run\node_modules\spawn-sync
> node postinstall

Installing native dependencies (this may take up to a minute)

npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Users\\Gary\\AppData\\Local\\atom\\app-1.7.1\\resources\\app\\apm\\bin\\node.exe" "C:\\Users\\Gary\\AppData\\Local\\atom\\app-1.7.1\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\Gary\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\Gary\\.atom\\.apmrc" "install" "C:\\Users\\Gary\\AppData\\Local\\Temp\\d-116319-5660-8y8hxo\\package.tgz" "--target=0.36.8" "--arch=ia32" "--msvs_version=2010"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! path C:\Users\Gary\.atom\.apm\debug\2.2.0\package\package.json
npm ERR! code EPERM
npm ERR! errno 50

npm ERR! Error: EPERM, rename 'C:\Users\Gary\.atom\.apm\debug\2.2.0\package\package.json'
npm ERR!  { [Error: EPERM, rename 'C:\Users\Gary\.atom\.apm\debug\2.2.0\package\package.json']
npm ERR!   errno: 50,
npm ERR!   code: 'EPERM',
npm ERR!   path: 'C:\\Users\\Gary\\.atom\\.apm\\debug\\2.2.0\\package\\package.json',
npm ERR!   parent: 'rocambole-linebreak' }
npm ERR! 
npm ERR! Please try running this command again as root/Administrator.
GeorgeWL commented 8 years ago

Same issue for when I just attempted to update:


> spawn-sync@1.0.15 postinstall C:\Users\GeorgeWL\AppData\Local\Temp\apm-install-dir-116515-10064-1rhjtls\node_modules\linter-js-standard\node_modules\happiness\node_modules\happiness-format\node_modules\esformatter\node_modules\npm-run\node_modules\spawn-sync
> node postinstall

Installing native dependencies (this may take up to a minute)

> spawn-sync@1.0.15 postinstall C:\Users\GeorgeWL\AppData\Local\Temp\apm-install-dir-116515-10064-1rhjtls\node_modules\linter-js-standard\node_modules\standard\node_modules\standard-format\node_modules\esformatter\node_modules\npm-run\node_modules\spawn-sync
> node postinstall

Installing native dependencies (this may take up to a minute)

> spawn-sync@1.0.15 postinstall C:\Users\GeorgeWL\AppData\Local\Temp\apm-install-dir-116515-10064-1rhjtls\node_modules\linter-js-standard\node_modules\semistandard\node_modules\semistandard-format\node_modules\standard-format\node_modules\esformatter\node_modules\npm-run\node_modules\spawn-sync
> node postinstall

npm WARN engine deep-extend@0.4.1: wanted: {"node":">=0.12.0","iojs":">=1.0.0"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine get-stdin@5.0.1: wanted: {"node":">=0.12.0"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine get-stdin@5.0.1: wanted: {"node":">=0.12.0"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine is-buffer@1.1.3: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Users\\GeorgeWL\\AppData\\Local\\atom\\app-1.8.0\\resources\\app\\apm\\bin\\node.exe" "C:\\Users\\GeorgeWL\\AppData\\Local\\atom\\app-1.8.0\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\GeorgeWL\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\GeorgeWL\\.atom\\.apmrc" "install" "C:\\Users\\GeorgeWL\\AppData\\Local\\Temp\\d-116515-10064-1kq1are\\package.tgz" "--target=0.36.8" "--arch=ia32"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! file C:\Windows\system32\cmd.exe
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! spawn-sync@1.0.15 postinstall: `node postinstall`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the spawn-sync@1.0.15 postinstall script 'node postinstall'.
npm ERR! This is most likely a problem with the spawn-sync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node postinstall
npm ERR! You can get their info via:
npm ERR!     npm owner ls spawn-sync
npm ERR! There is likely additional logging output above.

3.3.232,095
linter-js-standard
Linter plugin for JavaScript Standard Style
ricardofbarros
UPDATE TO 3.3.3SETTINGSUNINSTALLDISABLE
Settings
11:15 AM

So thinking it might be package manager throwing a hissy fit, attempted uninstalling in order to reinstall, this also kicked out an error

Failed to delete linter-js-standard: ENOTEMPTY, directory not empty 'C:\Users\GeorgeWL\.atom\packages\linter-js-standard\node_modules\babel-eslint\node_modules\babel-core\node_modules\regenerator\node_modules\commoner\node_modules\glob\node_modules\once\node_modules'

ricardofbarros commented 8 years ago

Hey @jagged3dge and @Georgiel, the packaged node.js and npm bins on apm are still very primitive versions of themselves. There is an weird error with node postinstall on lower npm versions with windows users. You can track the whole thing here on this issue.

Luckily we had this two PR 1 2 that updated the packaged ´node.js´ and npm bins.

As you can see on the tagged versions of apm the latest one is v1.12.5, this versions already has those two PR's merged. If you run on your console apm -v you should have something like this:

apm  1.9.2
npm  2.13.3
node 0.10.40
python ...

As you can see apm is still on a lower version with the node.js and npm bin outdated as well.

You could fix this if you update manually the apm bin to the latest version, but I can tell you that can be daunting task. I would just wait for the next atom to release, which will bring the newest apm.

NOTE: Atom released 1.9.0-beta1 just 5 days ago.

ricardofbarros commented 8 years ago

Also there is an active discussion here with this same issue. Please discuss there. Thanks. ❤️