hydrogen: Fail to install Hydrogen

Description:

Fail to install Hydrogen on a cleanly installed laptop

Steps to Reproduce:

Install windows 10
Install atom beta
Install Hydrogen

Versions:

Which OS and which version of Hydrogen and Atom are you running?

You can get this information from copy and pasting the output of atom --version from the command line.

Atom    : 1.23.0-beta1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0

Logs:

Please post any error logs and the output of the developer tools as described in our Debugging Guide.

fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open 'C:\Users\SPHS\.atom\packages\Hydrogen\package.json'
    at Error (native)
    at Object.fs.openSync (fs.js:640:18)
    at Proxy.fs.readFileSync (fs.js:508:33)
    at Proxy.fs.readFileSync (C:\Users\SPHS\AppData\Local\atom\app-1.23.0-beta1\resources\app\apm\node_modules\asar-require\lib\require.js:86:27)
    at C:\Users\SPHS\AppData\Local\atom\app-1.23.0-beta1\resources\app\apm\lib\install.js:476:42
    at fn (C:\Users\SPHS\AppData\Local\atom\app-1.23.0-beta1\resources\app\apm\node_modules\async\lib\async.js:582:34)
    at Immediate.<anonymous> (C:\Users\SPHS\AppData\Local\atom\app-1.23.0-beta1\resources\app\apm\node_modules\async\lib\async.js:498:34)
    at runCallback (timers.js:649:20)
    at tryOnImmediate (timers.js:622:5)
    at processImmediate [as _immediateCallback] (timers.js:594:5)

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 17 (13 by maintainers)

Most upvoted comments

@lgeiger This still doesn’t work on Ubuntu 16.04. Removing Hydrogen and then running apm install hydrogen downloads Hydrogen into ~/.atom/packages/Hydrogen, but it isn’t found in the command prompt. Even if I rename it to hydrogen and restart Atom, it still doesn’t find it.

kylebarron on Dec 20, 2017

I tried apm install hydrogen (lowercase), and it worked.

DerektheDev on Dec 19, 2017

@lgeiger I also got this error while upgrading to Hydrogen 2.2.0, despite using the command line.

> apm install Hydrogen
Installing Hydrogen to /home/kyle/.atom/packages ✓
fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/home/kyle/.atom/packages/Hydrogen/package.json'
    at Error (native)
    at Object.fs.openSync (fs.js:640:18)
    at Proxy.fs.readFileSync (fs.js:508:33)
    at Proxy.fs.readFileSync (/usr/share/atom/resources/app/apm/node_modules/asar-require/lib/require.js:86:27)
    at /usr/share/atom/resources/app/apm/lib/install.js:476:42
    at fn (/usr/share/atom/resources/app/apm/node_modules/async/lib/async.js:582:34)
    at Immediate.<anonymous> (/usr/share/atom/resources/app/apm/node_modules/async/lib/async.js:498:34)
    at runCallback (timers.js:649:20)
    at tryOnImmediate (timers.js:622:5)
    at processImmediate [as _immediateCallback] (timers.js:594:5)

It seems that up to 2.1.1, this package used a folder named ~/.atom/packages/hydrogen, with hydrogen in lower case, while in 2.2.0, it tries to install in ~/.atom/packages/Hydrogen, with Hydrogen in title case. Linux is case sensitive, so these are two different places. I’m guessing that’s the issue at play here.

While debugging, I uninstalled hydrogen, and then apm install hydrogen gave the traceback above. After also uninstalling hydrogen-launcher, apm install hydrogen gave a checkmark but then wasn’t recognized from Atom.

> apm install hydrogen                
Installing hydrogen to /home/kyle/.atom/packages ✓
> apm install hydrogen-launcher
Installing hydrogen-launcher to /home/kyle/.atom/packages ✓

kylebarron on Dec 18, 2017