Hacker GitHub

← All repos

vercel/next.js

View on GitHub ↗ ★ 143,463 JavaScript

The React Framework

197 mentions on Hacker News by 164 people: 28 stories, 169 comments · first 2016-10-25 · latest 2026-05-15

Mentions per year 197 mentions · busiest year 2025 (37)
20082026
AllStoriesComments NewestTopOldest
  1. …a known issue with embedding JSON. I found a dozen of related issues in the context of Next.js: * https://github.com/vercel/next.js/issues/40143 * https://github.com/vercel/next.js/discussions/39377 * https://github.com/vercel/next.js/discu…
    comment by punkpeye · 2026-03-02 · in Ask HN: Google started to index non-hyperlinks. What to do about it?
  2. …the Next.js version does. Is their behaviour actually the same? The rewrite looks incredibly naive. https://github.com/vercel/next.js/blob/b8cbaad24ca66ec673a7b... https://github.com/cloudflare/vinext/blob/main/packages/vine... Either way,…
    comment by slopinthebag · 2026-02-24 · in How we rebuilt Next.js with AI in one week
  3. …URL, add “quick” before github.com, and get AI-generated system design documentation in under 60 seconds. github.com/vercel/next.js → quickgithub.com/vercel/next.js The generated docs include a system overview, architecture breakdown, key…
    comment by stym06 · 2026-02-12 · in Show HN: QuickGitHub - Instant AI docs for any GitHub repo
  4. …of complaints on the NextJS subreddit, and here is a open thread on complaints with Turbopack https://github.com/vercel/next.js/discussions/77721 Looks the alternative is Rspack?
    comment by aggregator-ios · 2026-01-26 · in Turbopack: Building faster by building less
  5. …to load a Maplibre map server side, so the JS must be ready before the map starts to get loaded. https://github.com/vercel/next.js/discussions/86731
    comment by maelito · 2026-01-05 · in During Helene, I just wanted a plain text website
  6. > This isn't a Javascript problem, this is a React problem. It happened with Next.js as well https://github.com/vercel/next.js/discussions/11106 > Say Python ran in the browser natively, and you reimplented React on browser and server in…
    comment by ashishb · 2025-12-11 · in Denial of service and source code exposure in React Server Components
  7. This happens in Next.js as well https://github.com/vercel/next.js/discussions/11106
    comment by ashishb · 2025-12-11 · in Denial of service and source code exposure in React Server Components
  8. Here's a patch diff: https://github.com/vercel/next.js/compare/v15.0.4...v15.0.5 It looks like the fix is checking hasOwnProperty, so it's almost certainly an issue with prototype chain pollution.
    comment by bri3d · 2025-12-03 · in Critical RCE Vulnerabilities in React and Next.js
  9. …making continuous concessions that will lead to the ongoing spaghettification of toolchains. [1] https://github.com/vercel/next.js/discussions/65625
    comment by dvt · 2025-10-10 · in Vite+ – Unified toolchain for the web
  10. …on Vercel. Production-ready hosting part of the Framework is not Open Source nor well documented. https://github.com/vercel/next.js/discussions/59167 https://www.netlify.com/blog/how-we-run-nextjs/
    comment by cryptonym · 2025-10-09 · in The React Foundation
  11. …type (dev, prod local, prod) matters as well as the type of POST request. Link to my findings: https://github.com/vercel/next.js/issues/78070#issuecomment-...
    comment by elbajo · 2025-09-17 · in Next.js GET Cache Bypass via Multipart POST – Reproduces on Vercel.com
  12. …how I would expect. I had to use globalThis instead. And after all that I was still hit by this: https://github.com/vercel/next.js/issues/80445 It does work, but it was not great to set up. Granted, I went with the manual router (eg. not…
    comment by dminik · 2025-09-02 · in Next.js is infuriating
  13. …at school!" card for this issue, which will be old enough to attend elementary school next year: https://github.com/vercel/next.js/issues/10084
    comment by tyteen4a03 · 2025-09-02 · in Next.js is infuriating
  14. > Scientists discover a new super massive black hole at https://github.com/vercel/next.js/issues got me good
    comment by butlike · 2025-09-02 · in Next.js is infuriating
  15. …should first read through the 50 open and 71 closed GitHub issues related just to instrumentation ( https://github.com/vercel/next.js/issues?q=is%3Aissue%20stat... ), and make sure you understand all the undocumented ways in which…
    comment by ashwinsundar · 2025-07-27 · in Instrumenting Next.js with runtime secret injection
  16. …Next.js with App router (and with Pages being pushed out) is really bad for SPAs. See this thread: https://github.com/vercel/next.js/discussions/64660
    comment by csomar · 2025-06-12 · in Next.js 15.1 is unusable outside of Vercel
  17. …had to reverse-engineer a few details for more advanced features. This is being fixed now in https://github.com/vercel/next.js/discussions/77740 but that work is ongoing.
    comment by danabramov · 2025-06-02 · in Show HN: Kan.bn – An open-source alterative to Trello
  18. …that allow this functionality to be implemented on different platforms with a consistent API: https://github.com/vercel/next.js/discussions/77740 I don't think the push for RSC is at all motivated by the shady reasons you're suggesting. I…
    comment by liamness · 2025-06-01 · in Progressive JSON
  19. …responded to the issue back in January with a soft timeline It seems I missed that comment ( https://github.com/vercel/next.js/discussions/64660#discussi... ). My apologies. There were a lot of comments. I stand corrected, withdraw my…
    comment by antisol · 2025-05-31 · in Next.js: The "Versatile" React Framework That Can't Handle Dynamic Routes
  20. …advice and try a different framework instead of wasting time trashing on one you don't like. [0] https://github.com/vercel/next.js/discussions/64660#discussi...
    comment by lolinder · 2025-05-31 · in Next.js: The "Versatile" React Framework That Can't Handle Dynamic Routes
  21. (I'm on the Next.js team) We're working with Cloudflare on an official adapter. https://github.com/vercel/next.js/discussions/77740
    comment by leerob · 2025-05-09 · in Static as a Server
  22. for reference https://github.com/vercel/next.js/issues/48748
    comment by parham · 2025-03-31 · in You should know this before choosing Next.js
  23. yes, there is even the official example here https://github.com/vercel/next.js/tree/canary/examples/cache... but it does not work because of NextJS 15. I changed the example to point to latest NextJs 14 and fixed some cache-handler bugs it…
    comment by huksley · 2025-03-28 · in Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
  24. …cost effective, and fits their operational model. They are not willing to invest in that. [1] https://github.com/vercel/next.js/tree/canary/examples/cache...
    comment by eddythompson80 · 2025-03-27 · in Netlify deploys hundreds of thousands of Next.js sites – here's what challenging
  25. They actually appear to be working on "Interceptors" which is what you're describing; https://github.com/vercel/next.js/pull/70961
    comment by dbbk · 2025-03-24 · in Next.js version 15.2.3 has been released to address a security vulnerability
  26. …common (and previously recommended) middleware use-cases, rendering them almost completely useless: https://github.com/vercel/next.js/pull/77438
    comment by soulchild77 · 2025-03-24 · in Next.js and the corrupt middleware: the authorizing artifact
  27. …another header then checking to make sure it's still there afterwards, effectively an auth token: https://github.com/vercel/next.js/pull/77201/files )
    comment by cle · 2025-03-23 · in Next.js version 15.2.3 has been released to address a security vulnerability
  28. …external access list (one of them was vulnerable to SSRF) and there was never a CVE for it. https://github.com/vercel/next.js/pull/73482/files Source: https://news.ycombinator.com/item?id=43449986
    comment by czk · 2025-03-23 · in Next.js and the corrupt middleware: the authorizing artifact
  29. …an x-middleware-subrequest HTTP header with a colon-separated list of middleware names to skip. https://github.com/vercel/next.js/blob/v12.0.7/packages/next...
    comment by simonw · 2025-03-23 · in Next.js and the corrupt middleware: the authorizing artifact
  30. …similar vulnerabilities. I was made aware recently of a vulnerability that was fixed by this patch: https://github.com/vercel/next.js/pull/73482/files In this vulnerability, adding a 'x-middleware-rewrite: https://www.example.com ' header…
    comment by smlx · 2025-03-23 · in Next.js version 15.2.3 has been released to address a security vulnerability
  31. https://github.com/vercel/next.js/pull/75877 memory leaks in the runtime and frameworks all the time. This setTimeout leak crashed our prod machine multiple times until we rolled back.
    comment by dyl000 · 2025-03-10 · in Everything I Was Lied to About Node.js Came True with Elixir
  32. …empower.com/benchmarks/#section=data-r23&hw=... I discussed it with a couple of Next.js maintainers ( https://github.com/vercel/next.js/discussions/75930 ), and they indicated that it's only a problem for "standalone" deployments (i.e. not…
    comment by jonathanhefner · 2025-03-09 · in How much traffic can a pre-rendered Next.js site handle?
  33. Static builds with dynamic routes still broken with App Router: https://github.com/vercel/next.js/discussions/55393
    comment by BoorishBears · 2025-02-27 · in Next.js 15.2
  34. …file). It's a known issue (but rarely mentioned when you read about working with Next.js): https://github.com/vercel/next.js/issues/48748 I've never used MUI, but assuming that MUI is a barrel package, and you do the following: import {…
    comment by theogravity · 2025-02-23 · in Why we ditched Next.js and never looked back
  35. …requests to fix. We're working to allow access to all Node.js APIs in Middleware. Tracking here: https://github.com/vercel/next.js/discussions/71727 > The docs mention that you should treat Server Actions like public API endpoints and…
    comment by leerob · 2025-01-22 · in Next.js: An Honest Review
  36. …would be a lot more difficult and obviously they don’t want that. Do you want proof of that? https://github.com/vercel/next.js/discussions/46722 Check that whole conversation. It’s now closed with some bullshit because they don’t like…
    comment by 0xblinq · 2024-11-24 · in Show HN: Self-Host Next.js in Production
  37. - Layouts answer: https://github.com/vercel/next.js/issues/43704#issuecomment-... - Pass data to layout answer: https://github.com/vercel/next.js/discussions/44506#discussi... - For router.push one, I believe you're looking for this:…
    comment by leerob · 2024-10-11 · in Next.js, Just Why? (2023)
  38. …list some of them in case anyone is interested. - layout cannot access pathname of the current URL: https://github.com/vercel/next.js/issues/43704#issuecomment-... - App Router cannot pass data to layout:…
    comment by novoreorx · 2024-10-11 · in Next.js, Just Why? (2023)
  39. …so well enough to understand that tradeoff. That's why there is a supplemental API being added: https://github.com/vercel/next.js/pull/70961
    comment by leerob · 2024-10-10 · in Next.js, Just Why? (2023)
  40. …the most popular third party package for file watching (Chokidar) has a single dependency [3]. [1] https://github.com/vercel/next.js/blob/07a55e03a31b16da1d085... [2] https://github.com/swc-project/swc/blob/b94a0e1fd2b900b05c5f... [3]…
    comment by throwitaway1123 · 2024-09-26 · in Rewriting Rust
  41. …with it. You can disable it per individual link, or write & use a custom link component. [0] https://github.com/vercel/next.js/discussions/24437
    comment by prophesi · 2024-09-10 · in Show HN: YourNextStore – an open-source Shopify with Stripe as the back end
  42. …(not much content there though) with NextJS typescript markdown blog template https://github.com/vercel/next.js/tree/canary/examples/blog-... Now I am thinking about markdown editor, because writing content in VSCode, well, its ok, espe
    comment by sorokinvj · 2024-07-27 · in Ask HN: What is the best way to author blogs in 2024?
  43. Middleware can only use a subset of NodeJS APIs https://github.com/vercel/next.js/discussions/46722
    comment by mmarian · 2024-06-22 · in Is it Next.js server actions the future?
  44. Probably the most known example https://github.com/vercel/next.js/discussions/19065 It is not an issue if you host in Vercel. Implementing the requested feature would make the framework much better and easier to use when self-hosted…
    comment by nicce · 2024-06-09 · in A ChatGPT mistake cost us $10k
  45. …many intentional limitations that makes Next a very bad choice if you're self hosting. proof: https://github.com/vercel/next.js/discussions/46722
    comment by 0xblinq · 2024-04-04 · in Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
  46. https://github.com/vercel/next.js/discussions/46722 If only this had been brought to their attention recently with a bunch of good-faith discussion.
    comment by ervine · 2024-02-21 · in Remix Vite Is Now Stable
  47. …in your own infrastructure? And how about that dev rel... no response since August of last year. https://github.com/vercel/next.js/discussions/46722
    comment by ervine · 2024-02-21 · in Remix Vite Is Now Stable
  48. …this example doesn’t include the S in the acronym. sometimes I think the Next.js examples folder at https://github.com/vercel/next.js/tree/canary/examples is just an amazing example of how best to market a software product to developers…
    comment by bionhoward · 2023-12-28 · in BCHS software stack: BSD, C, httpd, SQLite
  49. …of concept of LTS or even any kind of thought on that topic when it comes to Next.js anyway (e.g. https://github.com/vercel/next.js/discussions/41906 ) At the end of the day, IMO the main difference is attitude. There is broad…
    comment by spion · 2023-12-25 · in What We Need Instead of "Web Components"
  50. …it more difficult to move to their platform later. They don't even respond anymore in the issue: https://github.com/vercel/next.js/discussions/46722 * They refuse to add a config file option to disable the telemetry. Yes, you can do the…
    comment by 0xblinq · 2023-12-07 · in Next.js, Just Why?