Closed TylerBarnes closed 2 years ago
Ok, I published a v2.3.1 that provides a no-op clearKeptObjects() to fix this issue (I believe this was the behavior before).
There is a little more work to be done to try provide a working clearKeptObjects() across different platforms, but this should get gatsby up and running at least. Let me know if you see any issues with this.
Thank you for the quick fix @kriszyp! I can confirm my builds are succeeding again 🙌
FYI, v2.3.2 should have working clearKeptObjects
functions across all supported node versions/platforms now.
Since the new release 4 hrs ago I'm running into this error via Gatsby which uses this package: