-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to install elm packages (on debian stable) #434
Comments
Installing everythin with the newest versions available from npm for debian ({"os":"linux","arch":"x64"}) also does not work $ npm -v Dependecies:
Side note:
not supported on linux:
|
Also tried with
(no improvement) as to one of the reference in issue #10
|
Hi @wibrt! Thanks for reporting this issue, have you tried one of those solutions suggested in #26 (comment)? |
Yes, the install works,
Just to make sure i use this elm binary, the same elm version is also globally installed.
|
In my opinion elm-create-app should avoid depending on npm installation of I think you might be able hotfix this on your machine by running this:
In addition you might need to |
For a reason that i don't understand, this works now. An upgrade to 4.2.13 (from 4.2.11) Thank you. |
I think the problem was that install.js script for npm installation elm didin't finish successfully so create-elm-app was calling into existing nodejs wrapper but this wrapper was unable to call the binary of compiler. |
what does "this problem" mean? If you get |
Okay so the Dockerfile is this
This is the output
As the container is running as root I am not quite sure whether permissions might be a problem here. Yet I might be completely wrong. Any pointers to further information, or tips are really appreciated. |
So this is where it fails for you: create-elm-app/scripts/create.js Lines 46 to 67 in 55547b0
Things to try:
|
So my /app folder is empty, as I want to create a new app into this, with create-elm-app.
Of course I don't have a /app/package.json. Now about
Yet, after this neither Thank you for your help so far, if there is anything more I can do, read, or try, I'm open to everything. |
npm (actually node itself I believe) has rules about how it goes about resolving node modules you can check it. If you don't have local |
Okay, after some parsing and figuring out, here is my solution:
So we need to go into It is sad that the plain |
My guess is that for security reasons npm doesn't run post-install scripts when being run as a root. This is understandable because allowing this means that package can do anything to your system during installation. |
Bug
after installing create-elm-app with npm
running (as user of root)
So there is a reference to issue 10,
all elm npm packages are installed globally
Environment
Packages are installed from debian stable if available, otherwise from npm
node -v
:v10.15.2npm -v
:5.8.0npm ls create-elm-app -g
(if you haven’t ejected):/usr/local/lib
└── create-elm-app@4.2.11
Then, specify:
Steps to Reproduce
The text was updated successfully, but these errors were encountered: