Grayson Hicks

I think the issue is still upstream with Preact not support React 18.

possible duplicate of #35110 ?

Just a note that this is more that just a warning for Gatsby. Unsafe builtin usage will result in the loss of incremental builds. So if a site updates one...

Also, this link describes the other way to fix this. (loadable-components to skip SSR being the other) ```javascript exports.onCreateWebpackConfig = ({ stage, loaders, actions }) => { if (stage ===...

The full error message as I was seeing is slightly different that the original posted above: ```javascript warning WebpackError: Unsafe builtin usage https.request at my_project-gatsby/node_modules/@algolia/client-search/dist/client-search.esm.js:129:1 at my_project-gatsby/node_modules/@algolia/cache-in-memory/dist/cache-in-memory.esm.js:18:1 at my_project-gatsby/node_modules/@algolia/client-recommendation/dist/client-recommendation.esm.js:9:18 at...

I believe it is compatible functionally and that is just a standard semver warning.

Added a fix for this here: https://github.com/oorestisime/gatsby-source-instagram/pull/238

Yes, this means the fetching from the API failed and no nodes were created.

@oorestisime I believe this is due to rate limiting and can be closed. There is possibly a solution using the Gatsby `cache` object to reduce the amount of fetching for...

More specifically, this can happen on any cloud build pipeline service because their IP range may be used very often to hit the API (not just your site building, but...