we're working hard on it! I'm leaning more towards sharing new things when they're fully ready but it is true that we could have shared a little more

we'll share more about this next week, but Turbopack is there to stay :)

yeah that's new in 15 :)

Let me know if you find something 🙏 a screenshot of the error would be enough

A common reason this can occur sometimes is that some browser extensions inject data attributes to the head or body during page load, which will fire React's alarms. Grammarly does this to me, for example. I recommend disabling extensions in dev.

Hey Maggie, I'm a team member; thanks for the report. I just tested on a fresh Next.js Boilerplate, and I could not repro it in dev or production.

Is that the template you used? If so, could you provide a screenshot of the error?

it’s gonna take us some time but we’re gonna get there 🫡

had a really promising chat with @orinokai.bsky.social today about how Netlify’s Next adapter works and how we could do better, we just need to ship now

That’s a really well written article 🙏 it’s quite interesting seeing our work from this perspective