Closed matthewmueller closed 2 minutes ago
Just for reference, I'm currently working round this by:
brew install vips
(via this issue thread)Looking at my history I think that was all I had to do
I did do the puppeteer/chromium steps, and got chromium installed, and I ran the brew install vips
command thoguh it failed. The command npm install
still kept failing. All errors seemed to be about dependencies, so searching StackOverflow led me to a couple of options: 1) downgrade to npm version 6, or 2) run npm install
with the --legacy-peer-deps
flag. That actually worked, and I was able to build locally and access the docs at http://localhost:8000/reference. (https://stackoverflow.com/questions/66239691/what-does-npm-install-legacy-peer-deps-do-exactly-when-is-it-recommended-wh)
tl;dr I am going to stick my assertion that our docs eco-system is far too complex. I'd like to eventually consider using something less heavy than Gatsby, for starters.
Outdated.
Right now you're unable to install the docs website locally on a Mac M1.
The problem appears to be because Gatsby wraps some binaries that aren't built for M1 yet. Hopefully it's just bumping some dependencies for M1 support.
So far we've discovered: