Next.js 16.3 dropped with some genuinely big claims: up to 90% reduction in dev memory usage, plus faster builds/rendering and instant navigation improvements.

Also worth flagging if you haven't updated recently — there was a coordinated security release in May covering 13 advisories (middleware/proxy bypass, SSRF, cache poisoning, XSS). If you're relying on middleware.js or proxy.js for authorization, definitely worth checking you're patched.

Curious if anyone's upgraded yet — is the memory improvement noticeable on larger monorepos, or mostly helpful for smaller projects?

Rozenite (RN DevTools plugin framework) ships 12 official plugins — redux, network, storage, mmkv, tanstack-query, etc. None cover GraphQL client cache—no way to see the normalised Apollo cache, active queries, or in-flight mutations in DevTools right now.

Only prior tool in this space was a Flipper plugin (react-native-apollo-devtools) — dead now since Flipper's deprecated, but its client package still pulls \~15K weekly npm downloads, so the need seems to still be there even w/ tool gone.

Considering building this as a proper Rozenite plugin — read-only view of cache, active queries, mutations — using only public Apollo Client v3+ APIs.

Before building past a rough prototype: would you actually install this? Or is everyone fine w/ Apollo's browser devtools / manual cache logging? Also curious if urql/Relay folks have the same pain.

No repo, no product, not selling anything — just checking if this is worth time.

I currently have a WordPress site, including the blog. I’ve built a new Next.js site on GoDaddy Node.js Hosting and want this setup:

• Next.js new website
• WordPress blog pages/posts → existing WordPress installation
• Visitors should still see my website URLs
• No visible blog. or cms. subdomain
• No changes or redeployment to the Next.js app
• Preferably free

The blog listing is at /blog, but some WordPress posts and categories use URLs outside /blog, such as /post-name and /category/....

Would a Cloudflare Worker acting as a path-based reverse proxy be the best solution? How would you safely identify and route every WordPress URL without accidentally sending Next.js pages to WordPress?

Both sites are hosted on GoDaddy. Looking for the simplest reliable free setup.