atom-ink icon indicating copy to clipboard operation
atom-ink copied to clipboard

Cannot install Ink

Open AxlRUI opened this issue 5 years ago • 12 comments

I tried a to purge and install atom again on ubuntu and nothing.

[email protected] postinstall /tmp/apm-install-dir-119717-13151-1ji4agk.eago/node_modules/ink node scripts/postinstall.js

Aborted (core dumped) npm WARN enoent ENOENT: no such file or directory, open '/tmp/apm-install-dir-119717-13151-1ji4agk.eago/package.json' npm WARN apm-install-dir-119717-13151-1ji4agk.eago No description npm WARN apm-install-dir-119717-13151-1ji4agk.eago No repository field. npm WARN apm-install-dir-119717-13151-1ji4agk.eago No README data npm WARN apm-install-dir-119717-13151-1ji4agk.eago No license field.

npm ERR! code ELIFECYCLE npm ERR! errno 134 npm ERR! [email protected] postinstall: node scripts/postinstall.js npm ERR! Exit status 134 npm ERR! npm ERR! Failed at the [email protected] postinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/axel/.atom/.apm/_logs/2019-08-17T16_46_17_378Z-debug.log

AxlRUI avatar Aug 17 '19 16:08 AxlRUI

I see something something very similar:

apm install ink                                                                                                               
Installing ink to /home/tracy/.atom/packages ✗

> [email protected] postinstall /tmp/apm-install-dir-119928-20182-kzzg9v.6uto/node_modules/ink
> node scripts/postinstall.js


Aborted (core dumped)
npm WARN enoent ENOENT: no such file or directory, open '/tmp/apm-install-dir-119928-20182-kzzg9v.6uto/package.json'
npm WARN apm-install-dir-119928-20182-kzzg9v.6uto No description
npm WARN apm-install-dir-119928-20182-kzzg9v.6uto No repository field.
npm WARN apm-install-dir-119928-20182-kzzg9v.6uto No README data
npm WARN apm-install-dir-119928-20182-kzzg9v.6uto No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! [email protected] postinstall: `node scripts/postinstall.js`
npm ERR! Exit status 134
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tracy/.atom/.apm/_logs/2019-10-28T21_44_59_366Z-debug.log

The contents of the log: 2019-10-28T21_44_59_366Z-debug.log

twadleigh avatar Oct 28 '19 21:10 twadleigh

I have the same problem. I'm on Pop!_OS 19.10 (Ubuntu) with

$>atom -v
Atom    : 1.41.0
Electron: 4.2.7
Chrome  : 69.0.3497.128
Node    : 10.11.0

and

$>apm -v
apm  2.4.3
npm  6.2.0
node 10.2.1 x64
atom 1.41.0
python 3.7.2
git 2.20.1

The installation fails with the same error message @AxlRUI and @twadleigh above had:

$>apm install ink
Installing ink to /home/kastner/.atom/packages ✗

> [email protected] postinstall /tmp/apm-install-dir-119931-29918-1y3a6qy.u69d/node_modules/ink
> node scripts/postinstall.js


Aborted (core dumped)
npm WARN enoent ENOENT: no such file or directory, open '/tmp/apm-install-dir-119931-29918-1y3a6qy.u69d/package.json'
npm WARN apm-install-dir-119931-29918-1y3a6qy.u69d No description
npm WARN apm-install-dir-119931-29918-1y3a6qy.u69d No repository field.
npm WARN apm-install-dir-119931-29918-1y3a6qy.u69d No README data
npm WARN apm-install-dir-119931-29918-1y3a6qy.u69d No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! [email protected] postinstall: `node scripts/postinstall.js`
npm ERR! Exit status 134
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kastner/.atom/.apm/_logs/2019-10-31T16_29_38_647Z-debug.log

2019-10-31T16_29_38_647Z-debug.log

fkastner avatar Oct 31 '19 16:10 fkastner

Alright, thanks to some debugging with @fkastner, we now know that having a system npm installed might be causing the problems.

A couple of things you could try are:

  • Uninstall npm before installing packages.
  • Make sure npm isn't on your PATH before installing packages.
  • Use apx to install julia-client and ink.

I don't know if any of the above work since I can't repro the bug, but please give them a go if time permits and report back.

pfitzseb avatar Nov 07 '19 10:11 pfitzseb

Doesn't help for me. After sudo mv /usr/bin/npm /usr/bin/npm.bak I have no longer an npm in my $PATH, but I still got the same error as before and as reported above by fkastner

MHellmund avatar Nov 11 '19 10:11 MHellmund

Do you still have node on your path, and if you do, can you try removing that was well?

pfitzseb avatar Nov 11 '19 11:11 pfitzseb

FWIW I also tried removing both but it didn't help either.

fkastner avatar Nov 11 '19 11:11 fkastner

Did anyone give apx a try?

pfitzseb avatar Nov 11 '19 12:11 pfitzseb

yes,

/usr/bin/npm install @aerijo/apx
~/node_modules/.bin/apx  install ink

worked without error.

MHellmund avatar Nov 11 '19 13:11 MHellmund

apx worked for me too. Before I could install it I had to update npm to the latest version

bramtayl avatar Feb 17 '20 14:02 bramtayl

I tried it again today with a fresh install of atom 1.44.0 and it still doesn't work with the same error message. Maybe we can get the atom developers to look at this again?

apx does work for me too.

fkastner avatar Feb 22 '20 14:02 fkastner

On a fresh profile and new Atom installation on Debian 10 (buster), uber-juno installation fail similarly on ink:

error Failed at the [email protected] postinstall script 

with the the main errors in the log seems to be:

2222 verbose stack Error: [email protected] postinstall: `node scripts/postinstall.js`
2222 verbose stack Exit status 134
2222 verbose stack     at EventEmitter.<anonymous> (/usr/share/atom/resources/app/apm/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16)
2222 verbose stack     at EventEmitter.emit (events.js:182:13)
2222 verbose stack     at ChildProcess.<anonymous> (/usr/share/atom/resources/app/apm/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
2222 verbose stack     at ChildProcess.emit (events.js:182:13)
2222 verbose stack     at maybeClose (internal/child_process.js:961:16)
2222 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)

I indeed have an installation of Debian's node (v10.15.2) and npm (5.8.0).

@MHellmund shell commands to use apx worked for me as well. Thanks!

pierre-haessig avatar Apr 24 '20 08:04 pierre-haessig

I have same problem in widows 7 32-bit my Julia is 1.5.0, Atom 1.5.0 tried reinstall uber-juno & julia-client but stll not install at all

AGMoAnalyst avatar Aug 20 '20 17:08 AGMoAnalyst