-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
"gatsby new" fails on eslint-loader #10620
Comments
Hi!
Right? |
Correct. I’m using an empty directory. Thank you! |
Thank you for opening this @bjpcjp Looks related to #9511
Can you check what version you have installed? |
Thanks @sidharthachatterjee - I'm using Python 3.6.5 via Anaconda. |
@bjpcjp That explains it
Can you please install and switch to |
Switched to Python 2.7.6 (Anaconda distro) and entered "$gatsby new homepy27" (empty directory). Compilation again failed. Error log:
|
Same issue on a fresh install. I'm also on python 2.7. |
Can you paste full terminal output? There might be some clues earlier |
@bjpcjp @brookslyrette Can you check if 3 is the default? I have a feeling node is still calling 3. After switching to 2.7 in Anaconda, can you run ?
|
This adds Python to output of `gatsby info` `gatsby-plugin-sharp` is very widely used and is included in the default starter. `sharp` uses `nodegyp` which needs `python` and according to its documentation > v2.7 recommended, v3.x.x is not supported We've seen several issues where building breaks due to `sharp` not working like #10620 and #9511 Knowing the python version in the env helps in these cases
@siddharthkp Root cause is the same as #9511. Installing the older version of plugin-manifest fixed it for now. #9511 (comment) |
This adds Python to output of `gatsby info` `gatsby-plugin-sharp` is very widely used and is included in the default starter. `sharp` uses `nodegyp` which needs `python` and according to its documentation > v2.7 recommended, v3.x.x is not supported We've seen several issues where building breaks due to `sharp` not working like gatsbyjs#10620 and gatsbyjs#9511 Knowing the python version in the env helps in these cases
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
We've seen several issues where builds break because `gatsby-plugin-sharp` fails for some reason. Typically because `sharp` didn't build correctly during install like in #10620 most likely due to an incorrect version of python From https://github.com/nodejs/node-gyp > python (v2.7 recommended, v3.x.x is not supported) This PR adds a try-catch around requiring `sharp` and bails early if it fails
Description
$gatsby new consistently fails to compile.
Steps to reproduce
$gatsby new home
Expected result
successful compilation
Actual result
Log from command line follows:
Environment
The text was updated successfully, but these errors were encountered: