Philippe Serhal

Hi folks. We're working on React 19 support. It's almost ready. We'll share an update in this thread when we have a canary release we can share with you all...

🚀 We've just shipped a preview of React 19 support in `gatsby@next`. We'd love if you all could give it a try and report back with any issues. 👉🏼 To...

Thank you for helping test @CSharperMantle! You can safely ignore this. It's a quirk of how the pre-release versions were published (I had initially published with the `react19` preid and...

@AntonPalmqvist Thank you for helping test! This is really helpful feedback. > 1. Can't resolve 'gatsby-core-utils/create-content-digest' in '/Users/anton/Git/antonpalmqvist-web/.cache/slice' Hrm, I bet this is a consequence of the duplicated `gatsby` packages...

Hi @eliorg, thanks for writing in! As far as we can tell, what's going on here is that `next/image` is rendering an `` tag that looks like this: ```html ```...

Hi @mparisot-antescofo! Though this isn't documented, I believe Next.js itself does not really support i18n when mixing App Router and Pages Router: https://github.com/vercel/next.js/issues/57704#issuecomment-1902683396. 😞 Hope that link helps.

Hi @syeddilawar4444. Thanks for writing in. We don't quite have enough information to effectively troubleshoot this as is. Could you please share your `netlify.toml`, `package.json`, and the command you are...

Thanks for sharing those details. First, `NETLIFY_NEXT_PLUGIN_SKIP` is an env var that tells us to skip using our next runtime! You shouldn't set that. However, I don't think this is...

I'm going to close this due to inactivity, but feel free to respond to my above message and I'll reopen it. Thanks!

@eduardoboucas cool to merge this?