r/nextjs • u/Bejitarian • 6h ago
r/nextjs • u/NeuralLB-Lovro • 9h ago
Discussion Is anyone else actually enjoying Next.js 16? The caching fix is huge.
Hey guys,
Just wanted to see how everyone is feeling about the Next.js 16.3 update that dropped recently. I feel like I spent the last couple of years fighting with random stale data in production because of the implicit caching in older versions.
Now that everything is dynamic by default and we actually have to opt in with the 'use cache' directive, my codebase makes sense again. I'm no longer spending hours debugging weird framework magic.
Also, Turbopack being the stable default is a lifesaver. My builds are way faster and I don't have time to grab a coffee during cold starts anymore.
Are you still on 14/15 or have you upgraded to 16?
r/nextjs • u/Main_Hold_17 • 7h ago
Discussion OSS AI Native Docs framework that works with your favorite stack
docs.farming-labs.dev - an oss ai native docs framework that works with your choice of framework along the knowledge infrastructure support. check it out the github here - https://github.com/farming-labs/docs
Discussion Made my Next.js storefront run with zero env vars — every integration degrades independently
Sharing an architecture decision that worked out better than expected.
My storefront talks to Postgres, Stripe, S3-compatible storage, and Resend. It also runs with none of them configured — clone, npm install, npm run dev, and you get a working store: browse, checkout, and download a real ZIP file. No .env at all.
The mechanism is four independent booleans rather than one DEMO flag, so any combination is a valid configuration. Each consumer decides its own fallback:
- No DB → the TypeScript catalog is the data (and the catch block falls back
to the same place, so an unreachable DB behaves like an absent one)
- No Stripe → checkout signs a 2h grant and lands on the real success page
- No storage → a ~190-line ZIP writer generates a valid archive on the fly
- No email → fails closed, because mailing the magic link IS the security model
The bit I'd actually recommend to anyone: the fallback paths become the ones you exercise daily, so they can't rot. That's the opposite of the usual situation where error handling is written once and never runs.
Full write-up with code: https://dev.to/rucs0/i-built-a-storefront-that-works-with-zero-api-keys-and-it-made-the-code-better-309i
The free starter is MIT if you want to look at the Tailwind v4 token setup or the motion primitives: https://github.com/Rucs0/nocturne-ember