Closed dandv closed 4 years ago
The error doesn't happen if I use npx yarn
instead of npm install
.
I've added to the gist yarn.lock
and the original package.json
.
I think this may be fixed if we update @pmmmwh/react-refresh-webpack-plugin
. The version we have installed includes a dependency on react-dev-utils, which has an exact dependency on an ancient version of browserslist. The new version of @pmmmwh/react-refresh-webpack-plugin removes that.
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! As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!
Thanks for being a part of the Gatsby community! 💪💜
Can you please provide a minimal reproduction? I don't see any in here.
Hi!
I'm going to close this now, as we can't do much to help without a reproduction. If you are able to create a minimal reproduction for this then please do answer here or reopen the issue. Thanks!
For me deleting the docker cashed files was the solution $ docker builder prune -a
Description
I'm getting this error on
gatsby develop
orgatsby build
, in what is AFAICT an identically set up Ubuntu 18 environment, with the only difference being that the error occurs on AWS Lightsail, but not locally. I usednpm ci
to make sure I install the same package versions - here's package-lock.json.Searching for the error shows it occurring with Parcel too.
Hopefully someone has a clue as to what the culprit is (browserlist?) and how to fix it.
Environment