Can't install themes or plugins.

[ghost]

@bluebelles27 commented on May 12, 2018, 8:08 PM UTC:

Prerequisites

• [X ] Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

I just downloaded Atom the other day and am trying to customize it. When I try to install a theme or plugin through Atom or the command line the installation always fails. I have added apm to the path variable. I was able to install some stuff that was featured by typing in apm featured install (12 packages installed). But when I typed in apm install material, for example, I get a failure. This is what the failure message lookslike

Steps to Reproduce

1. Try to install package through Atom
2. Try to install through command line

Expected behavior: Package or theme to be installed

Actual behavior: Error message such as the one shown below.

C:\Users\erink>apm install material
Installing material to C:\Users\erink.atom\packages fs.js:922
return binding.mkdir(pathModule._makeLong(path),
^

Error: ENOENT: no such file or directory, mkdir 'C:\Users\erink\AppData\Local\Temp;C:\php\d-118412-19192-1k62j86.iz035wmi'
at Error (native)
at Object.fs.mkdirSync (fs.js:922:18)
at Object.mkdirSync (C:\Users\erink\AppData\Local\atom\app-1.26.1\resources\app\apm\node_modules\temp\lib\temp.js:137:6)
at Request. (C:\Users\erink\AppData\Local\atom\app-1.26.1\resources\app\apm\lib\install.js:335:41)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at Request.onRequestResponse (C:\Users\erink\AppData\Local\atom\app-1.26.1\resources\app\apm\node_modules\request\request.js:1068:10)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)
at HTTPParser.parserOnIncomingClient [as onIncoming] `(_http_client.js:474:21)

Reproduces how often: Every time

Versions

C:\Users\erink>apm --version
apm 1.19.0
npm 3.10.10
node 6.9.5 x64
atom 1.26.1
python
git 2.16.1.windows.4
visual studio

Running Windows 10

Additional Information

Any additional information, configuration or data that might be necessary to reproduce the issue.

This issue was moved by rsese from atom/atom/issues/17313.

[rsese]

Thanks for the report @bluebelles27 - do you have any anti-virus running on your computer? If so, can you temporarily disable and try again?

Also, are you on a home network or a corporate/university network?

[ghost]

The only anti-virus I have on this computer is Windows Defender. I disabled it and tried again but had the same results. I am on a home network. I also just tried to replicate the issue on a different computer on the same network and was able to install themes and packages on the other computer.

[bastisawesome]

I have a similar issue on Arch Linux, latest versions of everything.

(node:2198) ExperimentalWarning: The fs.promises API is experimental
Installing atom-ide-ui to /home/bast/.atom/packages ✗

npm ERR! code ERR_STREAM_WRITE_AFTER_END
npm ERR! write after end

From the log file:

1728 verbose stack Error [ERR_STREAM_WRITE_AFTER_END]: write after end
1728 verbose stack     at writeAfterEnd (_stream_writable.js:243:12)
1728 verbose stack     at PassThrough.Writable.write (_stream_writable.js:292:5)
1728 verbose stack     at PassThrough.Writable.end (_stream_writable.js:582:10)
1728 verbose stack     at ReadEntry.entry.on (/usr/lib/node_modules/npm/node_modules/pacote/lib/extract-stream.js:19:41)
1728 verbose stack     at ReadEntry.emit (events.js:187:15)
1728 verbose stack     at ReadEntry.emit (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:296:25)
1728 verbose stack     at ReadEntry.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:249:12)
1728 verbose stack     at ReadEntry.end (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:162:27)
1728 verbose stack     at Unpack.[consumeBody] (/usr/lib/node_modules/npm/node_modules/tar/lib/parse.js:210:13)
1728 verbose stack     at Unpack.[consumeChunkSub] (/usr/lib/node_modules/npm/node_modules/tar/lib/parse.js:391:40)
1728 verbose stack     at Unpack.[consumeChunk] (/usr/lib/node_modules/npm/node_modules/tar/lib/parse.js:362:30)
1728 verbose stack     at Unzip.(anonymous function).on.chunk (/usr/lib/node_modules/npm/node_modules/tar/lib/parse.js:291:59)
1728 verbose stack     at Unzip.emit (events.js:182:13)
1728 verbose stack     at Unzip.emit (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:296:25)
1728 verbose stack     at Unzip.write (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minipass/index.js:99:17)
1728 verbose stack     at Unzip.write (/usr/lib/node_modules/npm/node_modules/tar/node_modules/minizlib/index.js:284:29)
1729 verbose cwd /tmp/apm-install-dir-118415-2198-1auekr0.0vax
1730 verbose Linux 4.15.12-1-ARCH
1731 verbose argv "/usr/bin/node" "/usr/lib/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/home/bast/.atom/.apm/.apmrc" "--userconfig" "/home/bast/.atom/.apmrc" "install" "/tmp/d-118415-2198-15ybm1y.9rx2/package.tgz" "--runtime=electron" "--target=1.8.4" "--arch=x64" "--global-style"
1732 verbose node v10.1.0
1733 verbose npm  v6.0.1
1734 error code ERR_STREAM_WRITE_AFTER_END
1735 error write after end
1736 verbose exit [ 1, true ]

OS: Linux 4.15.12-1-ARCH x86_64 GNU/Linux

Output from atom --version

Electron: 1.8.4
Chrome  : 59.0.3071.115
Node    : 8.2.1

[hansonw]

It looks like you installed Atom from pacman, which uses the wrong versions everywhere (Node, NPM, Electron, and Chrome all have the wrong versions in your output. Atom 1.26.1 is supposed to be using Electron 1.7.11, Node 7.9.0, etc).

Try installing Atom from the tarball on https://atom.io/releases.

From the apm install output you're using npm v6, which seems to be afflicted by this issue: npm/npm#19989

But Atom normally uses npm v3! e.g. on my Mac:

> /Applications/Atom.app/Contents/Resources/app/apm/bin/npm -v
3.10.10