You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gatsby new my-site fails trying to install gatsby-plugin-sharp. Without this dependency, the command works correctly. This makes it impossible for me to set-up a project with gatsby-starter-default or any starter based upon it.
2 main errors thrown are:
> [email protected] postinstall /Users/%username%/Desktop/my-site/node_modules/mozjpeg
> node lib/install.js
⚠ self signed certificate
⚠ mozjpeg pre-build test failed
ℹ compiling from source
✖ Error: Command failed: /bin/sh -c autoreconf -fiv
/bin/sh: autoreconf: command not found
at /Users/%username%/Desktop/my-site/node_modules/execa/index.js:231:11
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 0)
> [email protected] postinstall /Users/%username%/Desktop/my-site/node_modules/pngquant-bin
> node lib/install.js
⚠ self signed certificate
⚠ pngquant pre-build test failed
ℹ compiling from source
✖ Error: pngquant failed to build, make sure that libpng is installed
at /Users/%username%/Desktop/my-site/node_modules/execa/index.js:231:11
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 0)
I've followed the tutorial and have Node (not installed via homebrew but fully-functional), Xcode Command Line Tools & git installed.
Following the error message, I've also installed libpng which didn't produce any effect.
But none of them worked for me. 2 days ago the same command produced the expected result & initial configuration passed successfully. From that moment no significant events occurred in environment.
Steps to reproduce
Since I don't know why exactly this error happens, I cannot reproduce it, sorry.
Expected result
my-site should be configured & built
Actual result
2 errors were thrown. Initial configuration failed.
@LekoArts Thank you so much! Can't believe it finally works!
Below is the solution that worked for me:
Followed this, deleted CommandLineTools, re-installed again & updated them. The sequence was something like:
sudo rm -rf $(xcode-select -print-path)
xcode-select --install
softwareupdate -i -a
Installed Homebrew. If you are in Spain (I happened to be) installation instructions will not work and whatever you do, curl will throw either 60 (self-signed certificate) or 404 since whole https://raw.githubusercontent.com/ seems to be blocked because of unknown reason.
What you actually need to do is to fetch data from GitHub first and then to run downloaded local file, like this:
mkdir brew
cd brew
git clone https://github.com/Homebrew/install.git .
ruby install
You might need to install nvm with brew install nvm & re-start terminal. Since you might need to downgrade the node (I had to downgrade from stable to 8.11.3 for another project).
Install the whole bunch of libraries & configs that smartfolk recommend you to have:
Description
gatsby new my-site
fails trying to installgatsby-plugin-sharp
. Without this dependency, the command works correctly. This makes it impossible for me to set-up a project with gatsby-starter-default or any starter based upon it.2 main errors thrown are:
I've followed the tutorial and have Node (not installed via homebrew but fully-functional), Xcode Command Line Tools & git installed.
Following the error message, I've also installed
libpng
which didn't produce any effect.There are plenty of similar issues like:
#14015
papandreou/node-pngquant#14
But none of them worked for me. 2 days ago the same command produced the expected result & initial configuration passed successfully. From that moment no significant events occurred in environment.
Steps to reproduce
Since I don't know why exactly this error happens, I cannot reproduce it, sorry.
Expected result
my-site
should be configured & builtActual result
2 errors were thrown. Initial configuration failed.
Environment
The text was updated successfully, but these errors were encountered: