NPM install on linux fails #100
Comments
The The above will most likely give you a working and current version of Elm right now. Regarding the future of the changed installer, @rtfeldman should be able to diagnose the problem you encountered. |
thanks, that works. |
I communicated with @folkertdev via IRC about this problem. I got him setup with a fresh node/npm installation via nvm, and then he did a global install of elm with Very strangely, the output of his doing I have no idea why that's happening, and was not able to reproduce the problem in a fresh Ubuntu container, in which I followed the same steps for setting up nvm, node/npm, and elm@0.15.1. I did, though, discover that it's important to install |
There are more people (and still coming) apparently encountering the same problem in this thread. |
It's conceivable that this is an issue on older versions of npm, but I tried something in the upcoming #102 to work around it. We'll see... |
@folkertdev @michaelsbradleyjr I believe this is fixed in the latest (beta) release - can you try this and let me know if it works?
|
this works. Thanks! |
|
@mrmormon same here! By the way, @rtfeldman if you’d like |
@tomekwi, yes, the The problem, as you note, is that newer releases of Elm's npm package are, according to semver, older than the |
So npm appears to have weird rules for what version it chooses. I released 0.15.1-alpha and npm install elm still used 2.0.0. Same with Eventually I released 0.15.1 (no -beta extension), and npm install elm Then someone reported a bug and I released 0.15.1-beta4 to see if that It seems to be that it goes with the most recently published x.y.z release By that logic, next week when 0.16.0 comes out, that should become the new On Sat, Nov 14, 2015, 7:50 AM Michael Bradley ن notifications@github.com
|
By the way, my readme originally said “ |
Fixed now that the 0.16 installer is out. |
I just tried to install and I got the following error:
I am using 64bit Void linux. Attached is the full log - everything seems to be fine until the line 3589 |
Sounds like your machine doesn't trust bintray's cert. What do you see when visit this link? On Mon, Nov 23, 2015, 12:46 PM dusky3 notifications@github.com wrote:
|
I see the list of files:
|
That's bizarre...can't think of why npm would reject the cert but your browser would accept it. I assume if you try it again it gives the same result? (As in, not just a temporary fluke.) |
I tried twice last night, twice this evening and twice right now. Still the same error. |
Unfortunately I have no way to help with this. |
Anyway thank you for your time @rtfeldman. |
|
@dusky3 what happens if you upgrade your npm and try again? I'm successfully using the pre-release
|
@michaelsbradleyjr here is the output:
|
I upgraded to 5.0 and bingo! Thank you @michaelsbradleyjr . Now I can run elm, elm make, elm package and elm reactor without problems. The only command I can not run is elm repl which requires libtinfo-dev which is not available in my OS repositories:
But this is something I have to sort out myself. |
Concerning the |
@dusky3, is your OS an Arch linux? |
@jvoigtlaender Thank you for an advice, but I can't try it now. I will symlink ncurses tonight and will let you know if it worked. I am using 64bit Void linux: http://www.voidlinux.eu/ .. it is not an Arch fork, but I think there are some similarities with an Arch linux. |
@jvoigtlaender I can run elm repl without any problems after symlinking ncurses:
Thank you for all your help guys. |
I can't install Elm. Node setup in root: cd /root
ls -l bin
lrwxrwxrwx 1 root root 20 Jan 23 12:48 node -> ../lib/node/bin/node
lrwxrwxrwx 1 root root 19 Jan 23 12:48 npm -> ../lib/node/bin/npm
ls -l lib
lrwxrwxrwx 1 root root 21 Jan 23 12:47 node -> node-v5.5.0-linux-x64
drwxr-xr-x 6 root root 4096 Jan 23 2014 node-v0.10.25-linux-x64
drwxrwxr-x 7 500 500 4096 Jan 23 12:48 node-v5.5.0-linux-x64
drwxr-xr-x 5 nobody root 4096 Jan 23 12:45 node_modules node -v -> 5.5.0 npm install -g elm
npm install -g elm@2.0.0
npm install -g elm@0.15.1-beta4
I have no trouble installing other modules, such as coffee-script and less for instance. |
using
sudo npm install -g elm
does download and install everything (without errors), but the executables don't work, printing:the file
/usr/local/lib/node_modules/elm/index
(nor/usr/local/lib/node_modules/elm/index.js
) indeed doesn't exist.the
/usr/local/lib/node_modules/elm/share
directory also doesn't exist, nor does/usr/lib/node_modules/elm/share
nor is $ELM_HOME defined. Even though ELM_HOME doesn't need to be set by the user any more, is should still exist (right?).system: linux mint; npm version: 3.3.10
(update: after a clean reinstall, Elm is now installed in
/usr/lib/node_modules/elm
, but the same error persists)The text was updated successfully, but these errors were encountered: