Best tweets about Next.js
Discover the best tweets about Next.js, covering App Router, Server Components, caching, rendering, performance, deployments, releases, and architecture.
Specific Next.js features, App Router behavior, rendering, caching, performance, deployment, debugging, architecture, and production tradeoffs.
Best Next.js tweets
Ranked 01–40
@aurorascharff ·
View Transitions just got simpler with Next.js 16.2. <𝙻𝚒𝚗𝚔> now has a 𝚝𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗𝚃𝚢𝚙𝚎𝚜 prop. Tag your navigation with a type, and <𝚅𝚒𝚎𝚠𝚃𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗> picks the right animation.
Watch video
@nextjs ·
Next.js 16.2 • Up to ~60% faster rendering • Up to ~400% faster 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 startup • Server Function 𝚍𝚎𝚟 logging • Redesigned error page • Better hydration errors • 𝙴𝚛𝚛𝚘𝚛.𝚌𝚊𝚞𝚜𝚎 display in error overlay https://t.co/5NWBRWHzYV
@Railway ·
We moved Railway's entire frontend off Next.js. Two PRs, zero downtime. Builds went from 10+ minutes to under two. 200+ routes on @vite_js + @tan_stack Router, instant HMR, and dev server startup in seconds. @vrzgc's full breakdown: https://t.co/01jxBHWEqZ
@Hartdrawss ·
My exact tech stack for every client MVP in 2026 : After 50+ projects, I stopped experimenting. This stack ships fast and survives production. FRONTEND - Next.js 14 (App Router) - Tailwind CSS + shadcn/ui - React Query for server state - Zustand for client state - TypeScript. Always. BACKEND - Next.js API routes for straightforward MVPs - Node.js + Express when the API needs to be a separate service - Zod for input validation on every single endpoint DATABASE - Supabase (Postgres) for most projects - Drizzle ORM — type-safe, fast, no magic - Upstash Redis for caching and rate limiting AUTH - NextAuth.js or Supabase Auth - Never rolling custom JWT auth from scratch STORAGE - Cloudinary for images (free tier is generous enough for early MVPs) - Supabase Storage for documents and user uploads PAYMENTS - Stripe. Always Stripe. DEPLOYMENT - Vercel for frontend and Next.js API routes - Railway for standalone backends - Supabase for managed Postgres MONITORING - Sentry for error tracking (free tier covers early stage) - Vercel Analytics for frontend Total monthly cost for a new MVP before it gets traction: under $20. This exact stack has shipped projects that went on to close $50K+ in client contracts. Save it.
@nextjs ·
Next.js 16.2 introduces a stable Adapter API, built with Netlify, Cloudflare, OpenNext, AWS, and Google Cloud. But the API is only part of the story. Next.js is used by millions of developers across every major cloud, and making it work well everywhere is on us. Here are our commitments. https://t.co/ylGpJG3WpZ
@asidorenko_ ·
transitionType prop for Links in Next.js 16.2 (requires additional setup for <ViewTransitions />)
Watch video
@alex_barashkov ·
okay, now I get the TanStack Start hype. moved our app from the latest Next.js over the weekend, and the dev experience improved dramatically: 30GB RAM down to 2GB, much faster startup, and almost instant page loads even from a cold run. after spending the last few weeks trying to optimize our Next.js setup with AI and getting nowhere, i ended up using fewer tokens on the migration than we did on unsuccessful debugging/optimisation.
@alexcooldev ·
Why do most SaaS apps that don’t need SEO still overuse Next.js server-side rendering, making the app slower than client-side rendering? Use Vite + React for the app, and a separate Next.js project for the blog.
@aurorascharff ·
Gave the experimental 𝚗𝚎𝚡𝚝/𝚛𝚘𝚘𝚝-𝚙𝚊𝚛𝚊𝚖𝚜 inside "use cache" a spin with next-intl in Next.js 16.2. Cached components can read locale directly instead of prop-drilling it from the page. Updated my blog post with what I found ↓ https://t.co/U0NETwbbcT
@Tristan0x ·
Claude Code is a huge productivity unlock. As a career backend dev (with minimal React experience), I spent just a few hours on Sunday optimizing our frontend performance and our app now loads 75% faster! The beautiful thing is its able to run its own lighthouse tests, as well as perform chrome browser automation (`claude --chrome`) to validate/quantify results, then iteratively improve. Easy wins it picked up: * Convert all pngs to webp * Preload fonts with fallback * Inline icon SVGs for less network requests * Optimized imports and tree shaking using Nextjs optimizePackageImports for heavy deps * Lazy-loaded large SDKs and certain modals * Defer GraphQL client initialization until used * Create slick loading animations for charts and skeleton loaders for data fields Crazy to think how we could speed up the majority of web applications on the internet for the cost of a few dollars per site.
Watch video
@illyism ·
🚨 WARNING: If your Next.js robots.txt has Disallow: /_next, you're blocking all your CSS, fonts and JS from crawlers. Bots don't see your beautiful landing page. They see unstyled HTML soup. Crawlers now see your site like it's a raw HTML doc from 1984
@ctatedev ·
New: Next.js adapter for emulate Embed GitHub, Google, Slack, Apple, Microsoft, AWS, other emulators directly in your Next.js app One catch-all route, same origin, no CORS headaches. Every preview deployment just works. npx skills add vercel-labs/emulate --skill next
@michael_chomsky ·
this is pretty sick, next.js now has instant navigations and can prefetch shells instead of pages basically means that time between a click and a navigation is gone, time has caused me immeasurable emotional pain over the years
@southpolesteve ·
vinext is one month old today! It's a Vite plugin that reimplements the Next.js API surface. Your existing Next.js app, running on Vite. Deploy to Cloudflare Workers, Vercel, Netlify, AWS, or any Node.js server. It's just a Vite plugin, so `vite start` is all you need to ship to production. One of the biggest questions I got was "how will you maintain this?" The project was always about pushing the limits of what AI can do, and maintaining it has been no different. We use AI to triage, fix issues, review, merge PRs. The numbers over the last month: 395 merged PRs. 52 contributors. 34 releases in 27 days. It's been awesome to see a community form around this. Huge thanks to @James_Elicx, @Divkix, @hyoban_cc, @jokull, @Dayifour, @yunus25jmi, and everyone else who jumped in and shipped real code https://t.co/zGvTui0HGN
@aleyda ·
A must read for technical SEOs: Making Sense of Next.js Caching for Developers and SEOs by @WillKennard 👇 This piece to break down the core concepts of caching in Next.js from the perspective of a technical SEO: * Two Types of Page * Dynamic Routes, Suspense, and Hydration * What this means for SEOs and content teams: Workflows and considerations * More! Check it out: https://t.co/ojJSUmRCCg
@ctbbpodcast ·
@xssdoctor's CSPT research covers eight frameworks: https://t.co/fM5TAY3xa5 React Router's .replace(/%2F/g, "/") in matchPath has no i flag, so double-decode only works when the F in %252F is uppercase. This was reintroduced after a previous fix and is still in the codebase. Splat routes (path="files/*") match with (.*) instead of ([^\\/]+), so ../../admin works with zero encoding. Next.js uses the same await params API in page components and route handlers but they do opposite things. Page components re-encode through getParamValue(), route handlers fully decode through getRouteMatcher(). The traversal lands server-side. Ember's normalizePath() re-encodes % after decoding, which accidentally kills double-encoding. Wildcard params skip the final decodeURIComponent entirely, so they need literal ../ instead of encoded payloads. SvelteKit's param matchers reject bad values at the routing level before any load function even runs. Server load functions in +page.server.ts bypass hooks.server.ts, so auth middleware won't protect you. Nuxt's island component payload revival (revive-payload.client.js) is a stored CSPT sink. If you can poison window.__NUXT__, the key traverses the $fetch URL. (CVE-2025-59414)
@freeCodeCamp ·
Next.js apps are split between Server and Client Components, and it isn't always obvious how they should work together. In this tutorial, @webmekanic_ teaches you simple ways to pass data from Server Components to Client Components. You'll also learn which props can be passed safely, how to share data with Context and React.cache, and how to avoid environment poisoning. https://t.co/CuNrN2DLy1
@tomilola_ng ·
Vite is better than Next.js, for most SaaS dashboards Next.js is great when you need public pages, SEO, content, landing pages, blogs, and marketing routes. But for an authentication-gated SaaS platform? You probably don’t need half of what Next.js brings. Most SaaS dashboards are heavy client-side apps: Charts, Tables, Filters, Modals, Multiple State management, Role-based UI, Realtime updates, Admin workflows, Settings pages ... That is Vite territory. For me, the better setup is simple: -> Next.js for the marketing website. -> Vite + React for the actual SaaS dashboard. I use the right tool for the right surface, the UI below is still just a shell, but I’m building my SaaS one step at a time. #Pabbi is coming
@Hartdrawss ·
Just hit these numbers on a client Next[.]js build today ??!! LCP 0.40s. CLS 0.06. INP 8ms. heres exactly how i got there: [ step 1 — rendering strategy ] - most devs default everything to SSR and move on completely - that's poor strategy tbh; every route needs a decision. does this page change per user? - we mapped every route before writing a single component - this alone cuts your server response time significantly and it's quite a difference [ step 2 — nothing blocks the fold ] - went through every script loading above the fold like tracking scripts, font loaders, analytics - the browser should paint the page before it does anything else - Hard re-work but was able to clean it up; lazy loaded all of them so they only fire after the page fully paints [ step 3 — SEO infrastructure on day one ] - schema markup, OG tags, sitemap, robots.txt done and knocked out before any feature - crawl structure mapped properly so that google can actually index the right pages [ step 4 — assets compression ] - every image converted to webp, sized for the containers and a s3 integration - fonts subset to only the characters being used - videos compressed hard before the first commit TLDR; performance and SEO aren't a sprint you run before handoff but rather the foundation everything else sits on. if your site isn't ranking or loading slow on mobile don't blame the content !
@davidfowl ·
Want to deploy a Next.js app to Kubernetes without starting from YAML or hand-writing Helm? In @aspiredev 13.3, model the app, ingress, hostname, and TLS in your AppHost. aspire deploy turns that into a Helm-based deployment.
@kettanaito ·
I told this years ago: every framework is going implement RSCs in their own way and this is exactly where we are today. RSC between Next.js, TanStack Start, and React Router rely on the flight protocol alone, which is so low-level you cannot have a unified testing strategy.
@codebeast ·
I ran an experiment to test how Next.js would perform if it was handling 5000 web pages. The experiment accounts for dynamic pages and statically generated pages, build times, and performance in production. On @ThePracticalDev: https://t.co/YwrowyOIXP
@iamakulov ·
next.js (pages router) loads data for pages you navigate to, but never releases it, whoops: https://t.co/k03WTi36nn
@ldo_dev ·
My brain is fried but I'm grinning like a fool 😆 Yesterday I had only built web apps and now I've got a monorepo running two front ends with Next.js for web and Expo for mobile. Both apps share the same Prisma ORM setup and they share the same Hono API endpoints. One database, one API, multiple front ends. The best bit about this is that the technology is starting to make sense I can't wait to share what breaks next 🫡
@DmytroKrasun ·
Refactored Server Actions (Next.js) to oPRC. And damn, I envy AI that it will write code for me. The type safety and ergonomics are so sweet, it makes me want to code manually again.
@larsbuilds ·
My current deployment flow is pretty cool IMO 🤓 I do have a single node k3s Kubernetes cluster hosting all my SaaS apps as well as harbor and a single DB pod. Every SaaS app repo is a mono repo, holding the business logic mostly done in NextJS and sometimes a little python. The repo has a helm chart too. And I do have one repository with all my argo deployments in it. It uses the SaaS app repo git sha for the image and chart. Whenever I push to main of the SaaS repo: > image gets built and pushed to my harbor > image sha and helm chart sha is updated in the argo-deployments repo > this triggers a sync on argo and deploys my staging environment > some e2e tests run > if sucesfull a PR for prod is opened on argo-deployments > the PR description is generated by codex > every former PR for this app is closed > when merged prod gets updated
@codebeast ·
I wrote an article on how to deploy a Next.js 13 website including all the new features to @AWSAmplify: ✅ Deploy SSR ✅ Deploy SSG ✅ Deploy API Routes ✅ Deploy Image Optimization https://t.co/dI73Wr3Qfn
@melvynx ·
Average build time for TanStack Start: ~50 seconds Next.js: ~120 seconds More than 2x for the same application, same number of pages...
@davidfowl ·
Next.js apps get first-class aspire support in 13.3. Use fluent AppHost APIs to model the app, run it locally, and configure standalone publishing without hand-rolling Dockerfiles. #aspiredev @aspiredotdev
@Jilles ·
Last night I made the second part of my You Need A VPS Series: "Deploying Next.js to Production with Dokku and SQLite". No Vercel costs! I'm a huge Cloudflare Workers fan, but it's also really *fun* to own your own VPS for $4.64 and deploy apps to it. https://t.co/nt8NbxoRoE
@spikebrehm ·
finally got sick of painfully slow Next.js hot reload times, and issues with turbopack that forced us back to webpack we kicked off a Cursor cloud agent in GRIND MODE to migrate us to TanStack Start and 14 hours later it's still grinding…
@mauricekleine ·
how is a nextjs app on vercel with the whole stack in the same region still so laggy? my tanstack start app with a hono backend on AWS and a postgres database absolutely FLIES there are ZERO skeletons or spinners in the tanstack app... ...on a throttled 4G network no server components no cache components no opaque non-standard APIs no security mistakes that LLMs make all the time (auth only in layout.tsx and not in child page.tsx? it's safe bro!! (it's NOT)) just react and oRPC routers boggles the mind
@sentry ·
Next.js gives you SSR, routing, and edge runtimes for free, but its three-runtime architecture means errors hide, DB queries disappear behind ORMs, and server actions swallow useful messages before they hit the browser. Our latest blog post covers the specific observability gaps and how to close them with Sentry 😌 https://t.co/bvK3BRtozY
@Tabish_khan090 ·
🚀 #BuildInPublic — Canvo Whiteboard | Update 2.9 🔄 Replaced the standalone Express backend with Next.js API Routes 🔐 Powered authentication with #NextAuth ⚡ Unified the stack for a cleaner, faster & more scalable architecture #NextJS #NodeJS #Prisma #SaaS #BackendDevelopment
@saurra3h ·
if you're using @motiondotdev with the React Compiler in Next.js disable auto-compilation for motion components the compiler memoizes renders, but framer needs to re-run on every render to track element positions for layout and layoutId animations everything works locally but silently breaks in prod fix: reactCompiler: { compilationMode: "annotation" } and opt-in with "use memo" only on non-motion components let me know if any of you found better solution
@codeSTACKr ·
Here's the Next.js App Router pattern I use for agent frontends. Server actions for mutations, API routes for tokens. Clean separation.
@ThePracticalDev ·
A valid session, correct role, correct JWT, and a user could still read someone else's invoice. Here's the three-layer Next.js 16 auth model that catches what proxy.ts alone cannot. { author: @WDShubhra } https://t.co/SJ9WLEuLyJ
@ThePracticalDev ·
Next.js 16's 'use cache' directive gives no warnings when it silently fails. This dev built a free dev-only toolkit that surfaces cache misses, dynamic holes, missing cacheTag, and deprecated calls. { author: @WDShubhra } https://t.co/bt4xY5r6MO
@creowistech ·
🚨 How to Fix TypeScript isolatedModules Error in Next.js? If your Next.js build fails with this message: Re-exporting a type when isolatedModules is enabled requires using export type Don’t worry, it’s not a complex bug. It’s just about being clear with TypeScript. more...
@wickedguro ·
Something I don't understand how to do on Next.js Happy to hear from the next experts. My next config has images remotePatterns. It's all good if you just deploy next and have the env variables during the build. But what if I have a pre-built Docker with a Next app? How can I add the .env variables there, since this file is only used at build time? For now, I just changed all my <Image /> to <img /> because I don't see any solution.
Best Next.js tweets
Xholic studies what works in your niche, drafts posts in your voice and schedules them for the hours your audience is online.
$0 today · Cancel anytime
Browse all tweet collectionsKeep exploring