Getting started guide raises an error: npm install, node-gyp python2 couldn't be found #4359
Comments
|
Doing some research I understand I also understand My Any idea what I could be doing now? |
|
From a fresh From there, I get the error: |
|
I also tried update package.json with an updated version of sass-loader to: 12.1.0. No luck again, this raises a conflict when trying to npm install: So that's not helpful either. I'm a bit sad I'm getting stuck so early in the up and running guide, any idea what I might do now? |
|
Found a very helpful Nicd on libera.chat #elixir and got me unstuck 🙏 I updated my ... fine and let me run: ... without warning or error, so that sounds like a good workaround to me. This is the Also highlighting that this is a duplicate of: #4308, although I'm not too sure why it's close, so I'll leave this open for a bit. Also highlighting this merged PR that might be relevant: #4337. |
|
Sass has been removed from master in part to help avoid these kinds of problems. We have not yet backported the removal of sass for the v1.5 brach, but you can remove the sass npm deps, and the sass-loader from webpack config, then rename your app.scss to app.css, and changed the import in |
|
Hi @chrismccord 👋 Thank you so much for getting back to me! I'm curious how this is not an issue on your side exactly? I picked up the Up and Running guide and got straight into a whole bunch of errors. I had to go to a community chat and I was fortunate enough to get assistance to get through the very first steps. At least it sounds like a documentation problem, would this fit in a troubleshooting section for instance? That would have been helpful. |
|
This is very specific to node/npm which we include by default by shipping a webpack and package.json setup, but only affects some users on some systems as of recent. We have addressed this by removing sass from the phx.new generator in 1.6 which is due out very soon, but in the end the root problem is not in any of our sources. I understand that it's frustrating for users to hit this, and we especially don't want newcomers to hit any friction, but this is literally not something we can solve since the problem is on node/npm/node-sass/etc. We've taken necessary steps to mitigate problems for people and a release will be out soon :) |
Environment
Arch Linux, uname -a:
Expected behavior
The getting started guide doesn't fail in early steps.
Actual behavior
Just started following the up and running guide on the phoenix documentation for version 1.5.9 at: https://hexdocs.pm/phoenix/up_and_running.html#content.
Running the first step is fine:
... which logs, including instructions:
From there, I go into the next step:
... which raises:
I am not familiar with
npmbut I thought this part would be straightforward, any idea what is going here?The text was updated successfully, but these errors were encountered: