50 Best Tweets About Next.js (2026)

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.

Creators
43
Updated

What 50 top Next.js posts reveal

Next.js discussion combines release and deployment updates with practitioner-reported tradeoffs in rendering, SEO, debugging, security, and developer experience. High-scoring outliers include posts about Next.js 16.2, a Turbopack memory-efficiency improvement, and Railway’s frontend migration.

Dominant tone
Positive

46% of posts

Median score
21.3

All-time engagement

Leading format
Announcement

28% of posts

Recent posts
14%

Published in 90 days

Conversation map

The themes creators return to

Framework comparisons and migrations

Comparisons or moves between Next.js and Vite, TanStack Start, React Router, Framer, Webflow, and vinext, especially for SaaS dashboards and developer workflow tradeoffs.

36%

Performance, builds, and developer experience

Runtime speed, Core Web Vitals, bundle and asset optimization, Turbopack memory use, build times, hot reload, dev startup, HMR, and production benchmarks.

36%

Rendering, Server Components, and caching

SSR, SSG, ISR, client rendering tradeoffs; Server/Client Component data flow; Server Actions; React Server Components; and use cache behavior.

24%

Deployment, infrastructure, and portability

Deploying Next.js across Vercel, AWS Amplify, Cloudflare, Kubernetes, Docker, VPS/Dokku, Aspire, adapters, and environment-specific build configuration.

20%

Next.js releases and framework features

New Next.js capabilities including 16.2 improvements, View Transitions, Link transition types, instant navigation, prefetching, Adapter API, root params, and App Router patterns.

16%

Security, authorization, and supply-chain risk

Critical vulnerabilities, route and parameter traversal issues, auth enforcement, environment secrets, Vercel incidents, and dependency or platform security concerns.

16%

Debugging, observability, and production reliability

Hydration and error diagnostics, Sentry observability gaps, cache debugging, runtime-specific failures, React Compiler compatibility, and memory leaks.

10%

SEO, crawlability, and bot-rendered content

Ensuring Next.js and JavaScript sites expose server-rendered or static HTML to search engines and LLM crawlers, including robots.txt and rendering diagnostics.

8%

Tone and stance

Sentiment Positive leads
Author posture Supportive leads

Performance benchmark

Median likes
83
Median reposts
6
Median replies
6
Median views
5.7K

Posts with media make up 52% of this collection. Their median all-time score is 27.5, compared with 10.2 for text-only posts.

Format mix

  • Announcement 28% · score 38.9
  • Case Study 28% · score 25.2
  • Opinion 20% · score 9.37
  • Tutorial 20% · score 23.0

Where creators agree, and where they do not

Shared view

Next.js 16.2 draws attention for UX and tooling

Posts highlight Link transition types for View Transitions, reported rendering and dev-startup improvements, and improved Server Function logging and hydration/error diagnostics in Next.js 16.2.

Shared view

Rendering strategy should be intentional

One author argues against defaulting SaaS routes to SSR. Other posts recommend selecting rendering approaches by route needs and using SSG, SSR, or ISR where rendered output and crawlability matter.

Open debate

Next.js versus Vite for SaaS dashboards

Migration and opinion posts favor Vite or TanStack Start for some client-heavy dashboards, citing their reported build, startup, HMR, or memory experiences. Another post positions Next.js for public, SEO-oriented surfaces.

Open debate

Performance claims vary by implementation

Next.js 16.2 announces up to roughly 60% faster rendering and up to roughly 400% faster dev startup, while migration posts report faster builds or lower memory use after moving elsewhere. A separate benchmark post says identical-app comparisons were run at 1,000 req/s on AWS EKS, but does not include the results in the tweet.

Open debate

Operational concerns are reported across security and debugging posts

Posts describe route and parameter decoding behavior, a reported vulnerability, cache-debugging gaps, observability challenges, and a production-only interaction between React Compiler and Motion. These are reported experiences and claims in the cited posts, rather than a quantified incidence rate.

Patterns behind standout posts

Media posts outperform text-only posts

Deterministic analytics report 26 posts with media (52%). Their median all-time score is 27.47, versus 10.22 for text-only posts. Cited outliers include release, optimization, and migration posts.

Release and case-study formats lead engagement

Announcements and case studies each account for 14 posts (28%). Their median all-time scores are 38.9 and 25.23, respectively. Cited examples cover Next.js 16.2, a Turbopack optimization, and a frontend migration.

Feature posts are the strongest thematic performers

The releases-and-features theme has the highest reported theme median all-time score, at 157. Its cited examples cover View Transitions, diagnostics, and experimental root-params use with the use cache directive.

Statistical standouts

  1. View standout post 1 Score 556.3 · 26.1× median
  2. View standout post 2 Score 554.1 · 26× median
  3. View standout post 3 Score 532.0 · 24.97× median
  4. View standout post 4 Score 493.2 · 23.14× median
  5. View standout post 5 Score 454.9 · 21.35× median

Who shapes this conversation

The five most represented creators account for 20% of the selected posts.

  1. 1. Aurora Scharff

    @aurorascharff

    2 posts

  2. 2. Christian Nwamba

    @codebeast

    2 posts

  3. 3. Critical Thinking - Bug Bounty Podcast

    @ctbbpodcast

    2 posts

  4. 4. David Fowler

    @davidfowl

    2 posts

  5. 5. Daniel Foley Carter

    @foley_seo

    2 posts

  6. 6. Next.js

    @nextjs

    2 posts

Repeat contributors cover releases, caching, and deployment

Among 43 creators, Next.js, Aurora Scharff, and Christian Nwamba each appear twice in the top-voice list. Their cited posts cover release updates, caching experimentation, and AWS Amplify deployment guidance.

Migration stories are prominent among cited posts

Railway’s migration post has an all-time score of 532.02 and is listed as an outlier. Alex Barashkov’s cited migration post reports moving an app from Next.js to TanStack Start and describes lower memory use and faster startup in that setup.

Security-focused accounts appear among repeat contributors

Critical Thinking - Bug Bounty Podcast appears twice in the top-voice list. Its cited posts discuss parameter traversal and server-side implications in hybrid frameworks, including Next.js.

Since the previous snapshot

What changed since Aug 12, 2026

  • 80% of the selected posts remained.
  • The creator count changed by +2.
  • The leading sentiment remained stable.
How this analysis was made

Themes, sentiment, stance, and post format are classified per tweet. All counts, shares, medians, creator concentration, freshness, and performance comparisons are then calculated directly from the published snapshot.

Xholic's all-time score compares engagement while accounting for reach, post age, and creator consistency. It is used for relative comparisons within this collection.

This report analyzes the exact 50-post snapshot shown below. AI identifies editorial categories and drafts explanations; all statistics are calculated from the snapshot, and every narrative claim is checked against cited posts before publication.

Top Next.js tweets from 43 creators

Ranked 01–50

  1. 01

    @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.

    Video thumbnail from Aurora Scharff's post Watch video
    • 28 Replies
    • 96 Reposts
    • 1.2K Likes
    • 64.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  2. 02

    @rauchg ·

    Fable just found a 15-30% memory efficiency improvement in Turbopack / Next.js, nearly autonomously. @tobi asked me today: what have been your “holy s***” moments with AI? My answer was: it’s every single week. And it’s accelerating. In fact, “WTFs/day” might just be my

    • 131 Replies
    • 195 Reposts
    • 4.6K Likes
    • 467.3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  3. 03

    @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

    • 101 Replies
    • 214 Reposts
    • 3.2K Likes
    • 548.3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  4. 04

    @prasenx ·

    Next.js just got its worst vulnerability ever, CVSS 8.6. → affects versions 13.4.13+, 14.x, 15.x, and 16.0.0–16.2.4 → attackers can access your internal services, cloud credentials, API keys, and admin panels → no authentication needed → one crafted request is all it takes →

    Video thumbnail from Prasenjit's post Watch video
    • 124 Replies
    • 318 Reposts
    • 2.5K Likes
    • 854.9K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  5. 05

    @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

    • 150 Replies
    • 395 Reposts
    • 4.2K Likes
    • 452K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  6. 06

    @matteocollina ·

    We benchmarked TanStack Start, React Router, and Next.js running the exact same eCommerce app at 1,000 req/s on AWS EKS. The results were eye-opening.

    • 97 Replies
    • 207 Reposts
    • 2.3K Likes
    • 375.6K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  7. 07

    @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

    • 0 Replies
    • 13 Reposts
    • 52 Likes
    • 0 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  8. 08

    @asidorenko_ ·

    transitionType prop for Links in Next.js 16.2 (requires additional setup for <ViewTransitions />)

    Video thumbnail from Alex Sidorenko's post Watch video
    • 7 Replies
    • 32 Reposts
    • 502 Likes
    • 31.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  9. 09

    @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

    • 89 Replies
    • 327 Reposts
    • 2K Likes
    • 909.4K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  10. 10

    @wesbos ·

    Next.js just shipped an Adapter API, allowing you to deploy to any platform All features supported on any infrastructure. Netlify, Cloudflare, AWS Amplify, and Google Cloud etc.. This is huge and I applaud the Next team for working on this

    • 40 Replies
    • 54 Reposts
    • 1K Likes
    • 71.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  11. 11

    @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

    • 37 Replies
    • 23 Reposts
    • 680 Likes
    • 60.4K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  12. 12

    @jaydwivedi_ ·

    Kree8 website will NOT lag now! Just ditched Framer and we'll be coding our future client websites - glad we took another risk of trying something new No-code tools are great… until you care about performance. I was so shocked to see how our website worked on Safari, and I

    Video thumbnail from Jay Dwivedi's post Video thumbnail from Jay Dwivedi's post Watch video
    • 60 Replies
    • 14 Reposts
    • 451 Likes
    • 50.4K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  13. 13

    @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.

    • 74 Replies
    • 9 Reposts
    • 404 Likes
    • 43K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  14. 14

    @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

    • 6 Replies
    • 10 Reposts
    • 127 Likes
    • 4.9K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  15. 15

    @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

    Video thumbnail from Tristan's post Watch video
    • 27 Replies
    • 12 Reposts
    • 199 Likes
    • 17.5K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  16. 16

    @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

    • 5 Replies
    • 14 Reposts
    • 148 Likes
    • 8.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  17. 17

    @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

    • 9 Replies
    • 5 Reposts
    • 90 Likes
    • 12K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  18. 18

    @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

    • 6 Replies
    • 6 Reposts
    • 161 Likes
    • 7.9K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  19. 19

    @foley_seo ·

    Optimizing your site for SEO & for LLMS? It's CRUCIAL that user-agents / bots are actually able to see the rendered output. Not all tech stacks are suitable out of the box - JS tech stacks are notorious for: 1. Not being easy to render even for Googlebot which can render JS

    • 6 Replies
    • 5 Reposts
    • 32 Likes
    • 2.3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  20. 20

    @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.

    • 1 Replies
    • 16 Reposts
    • 119 Likes
    • 18K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  21. 21

    @ctbbpodcast ·

    Query params have a structural advantage over path params for CSPT because path params get split on / during route matching, so your payload has to survive inside a single segment, while query params have no segment boundary and the entire string ../../api/internal/users lands as

    • 0 Replies
    • 7 Reposts
    • 70 Likes
    • 3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  22. 22

    @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

    • 7 Replies
    • 13 Reposts
    • 219 Likes
    • 17.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  23. 23

    @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

    • 0 Replies
    • 22 Reposts
    • 111 Likes
    • 5.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  24. 24

    @tan_stack ·

    Independent benchmark: @Platformatic put TanStack Start, React Router, and Next.js under load and shared the results. Worth a read if you care about SSR performance beyond toy benchmarks. https://t.co/D7ntpzaXp3

    • 8 Replies
    • 22 Reposts
    • 200 Likes
    • 41.4K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  25. 25

    @JohnPhamous ·

    in the worlds oldest and largest nextjs codebase PRs now merge 66% faster (p50) and 83% faster (p90) - guardrails for shipping faster & safe - cut the noise from test outputs

    • 6 Replies
    • 3 Reposts
    • 124 Likes
    • 10.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  26. 26

    @melvynx ·

    I try to migrate my app from Next.js to Tanstack Start : build time is literally divided by 2

    • 11 Replies
    • 6 Reposts
    • 171 Likes
    • 22.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  27. 27

    @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

    • 10 Replies
    • 0 Reposts
    • 43 Likes
    • 1.9K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  28. 28

    @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.

    • 6 Replies
    • 9 Reposts
    • 80 Likes
    • 6.1K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  29. 29

    @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.

    • 3 Replies
    • 4 Reposts
    • 16 Likes
    • 613 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  30. 30

    @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.

    • 4 Replies
    • 1 Reposts
    • 85 Likes
    • 13.1K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  31. 31

    @BradfordHuber4 ·

    Some more thoughts on @webflow & why I've started building with Claude Code on a custom stack. I see a lot of people talking about how this kind of stack is only good for developers & technical people. If I believed that was true I'd still be building on @webflow . Ultimately

    • 3 Replies
    • 3 Reposts
    • 29 Likes
    • 1.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  32. 32

    @TosinOlugbenga ·

    Using the MCP Server is the most powerful tool you can give to your AI. Wired up an application with Lovable which uses Vite + React. Connected the code to GitHub and cloned it to my IDE. And then asked my AI agent to use next-dev MCP to convert the app from react vite to

    • 6 Replies
    • 2 Reposts
    • 19 Likes
    • 2.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  33. 33

    @sadkatwt ·

    What should you choose? Fullstack or a decoupled approach which is basically seprate frontend and backend. Choosing your app architecture depends on your specific goal - Option A - Separate Frontend and Backend This is the standard for professional, scalable apps where the UI

    • 7 Replies
    • 0 Reposts
    • 19 Likes
    • 645 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  34. 34

    @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

    • 3 Replies
    • 21 Reposts
    • 110 Likes
    • 12.9K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  35. 35

    @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,

    • 6 Replies
    • 0 Reposts
    • 20 Likes
    • 898 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  36. 36

    @iamakulov ·

    next.js (pages router) loads data for pages you navigate to, but never releases it, whoops: https://t.co/k03WTi36nn

    • 4 Replies
    • 0 Reposts
    • 29 Likes
    • 5.1K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  37. 37

    @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.

    • 6 Replies
    • 1 Reposts
    • 27 Likes
    • 2.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  38. 38

    @tempoimmaterial ·

    Last month, a Cloudflare engineer rebuilt 94% of Next.js in a week for $1,100 in tokens. If your code can be regenerated by a better model next quarter, your Git history was never your moat. But then last week, another Cloudflare fork of a Vercel project hit... but the clone

    • 0 Replies
    • 1 Reposts
    • 16 Likes
    • 6.4K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  39. 39

    @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

    • 3 Replies
    • 0 Reposts
    • 6 Likes
    • 473 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  40. 40

    @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

    • 1 Replies
    • 0 Reposts
    • 23 Likes
    • 3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  41. 41

    @foley_seo ·

    A HUGE amount of the web is becoming less accessible to AI and search engines because a HUGE amount of vibe coders are not understanding that VIBE CODING produces APPS by default. Apps do not need to be indexed, so they aren't built for "SEO" or "indexability" they're built for

    • 2 Replies
    • 0 Reposts
    • 4 Likes
    • 331 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  42. 42

    @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…

    • 5 Replies
    • 0 Reposts
    • 10 Likes
    • 2.6K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  43. 43

    @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

    • 3 Replies
    • 0 Reposts
    • 4 Likes
    • 291 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  44. 44

    @MaheshPawaar ·

    vercel got hacked. a threat actor claiming to be shinyhunters is selling stolen data for $2 million on breachforums. vercel confirmed unauthorized access to internal systems on april 19, 2026. here's everything you need to know. > how it happened: the entry point wasn't a

    • 0 Replies
    • 0 Reposts
    • 8 Likes
    • 167 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  45. 45

    @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

    • 0 Replies
    • 0 Reposts
    • 7 Likes
    • 781 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  46. 46

    @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

    • 0 Replies
    • 0 Reposts
    • 2 Likes
    • 141 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  47. 47

    @codeSTACKr ·

    Here's the Next.js App Router pattern I use for agent frontends. Server actions for mutations, API routes for tokens. Clean separation.

    • 2 Replies
    • 1 Reposts
    • 2 Likes
    • 243 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  48. 48

    @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

    • 0 Replies
    • 1 Reposts
    • 9 Likes
    • 3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  49. 49

    @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

    • 2 Replies
    • 1 Reposts
    • 7 Likes
    • 2.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  50. 50

    @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

    • 2 Replies
    • 0 Reposts
    • 2 Likes
    • 539 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.

Explore more of the best tweets on X.

Browse all tweet collections

Tweet Remixer

Remix this post

Creator

@creator

View on X

Choose a tone