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. …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
  2. ▲ 3
    Vercel/Next.js memory leak in Fetch API
    story by inex · 2024-08-07 · 0 comments
  3. …(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?
  4. 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?
  5. 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
  6. …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
  7. 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
  8. …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
  9. …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
  10. …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"
  11. …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?
  12. ▲ 2
    Ask HN: How does Nextjs justify using React canary branches?
    story by prng2021 · 2023-11-19 · 1 comment
  13. Not sure. I just read the code. https://github.com/vercel/next.js/blob/ffdfd33251165d8b2f092...
    comment by bottlepalm · 2023-11-03 · in Write PHP Code Within Next.js Components
  14. This should be supported: https://github.com/vercel/next.js/discussions/44628#discussi...
    comment by leerob · 2023-10-28 · in Why I'm using Next.js
  15. …running in front of every request in your application. We're still evaluating options here: https://github.com/vercel/next.js/discussions/46722#discussi...
    comment by leerob · 2023-10-28 · in Why I'm using Next.js
  16. …open for a month now and has affected a lot of people but it seems like Vercel just doesn't care. https://github.com/vercel/next.js/issues/56018
    comment by lucasmerlin · 2023-10-28 · in Why I'm using Next.js
  17. …jump to mind: Server actions don't work in parallel routes unless that route was hard navigated: https://github.com/vercel/next.js/issues/54173 Parallel routes don't unmount if navigated from with anything other than router.back()... this…
    comment by cockatiel_day · 2023-10-27 · in Next.js 14
  18. …only for him to tell me that they had been having the same issue, and linked to this thread. https://github.com/vercel/next.js/issues/54708 Working with a web framework that's so unstable that fundamental features like the devserver break…
    comment by jowday · 2023-10-26 · in Next.js 14
  19. https://github.com/vercel/next.js/issues/22319 https://github.com/vercel/next.js/discussions/46722 Let us take control when self-hosting, please!
    comment by ervine · 2023-10-26 · in Next.js 14
  20. …of NextJs suddenly breaking major things in minor releases: Environment variables stopped working: https://github.com/vercel/next.js/issues/53367 The <Image> component stopped working: https://github.com/vercel/next.js/issues/53715 (Both…
    comment by Palmik · 2023-10-26 · in Next.js 14
  21. …out how it bundles and sends the entire react-dom library twice to every user on every page view https://github.com/vercel/next.js/issues/51508 . Fuck 1MB of JS to render a static HTML page. Fuck the image component, and not being able to…
    comment by orf · 2023-10-26 · in Next.js 14
  22. ▲ 81
    Next.js v13 websites are a heaven for scraping
    story by punkpeye · 2023-10-14 · 35 comments
  23. …That optimization comes at a cost that I think is best visible in this GitHub issue: https://github.com/vercel/next.js/discussions/42732 As someone who runs Next.js with a custom server setup on a VPS, I think the haydays of Next.js are…
    comment by flagged24 · 2023-09-28 · in Ask HN: Risk of Vendor Lock-In with Next.js
  24. https://github.com/vercel/next.js/issues/55161 Canary did the trick
    comment by flagged24 · 2023-09-16 · in GitHubGuessr
  25. …supporting the Edge runtime. This borders vendor lock-in and continues to be an ongoing debate: https://github.com/vercel/next.js/discussions/46722 . Hope they add the ability to switch to Node.js runtime.
    comment by jcoletti · 2023-09-14 · in Next.js, Just Why?
  26. Some interesting background on why Next.js's middleware doesn't support Node.js on GH here: https://github.com/vercel/next.js/discussions/46722 This feels like somewhere where you can really see the conflict between "Next.js is a…
    comment by pimterry · 2023-09-09 · in Next.js, Just Why?
  27. For Context support, https://github.com/vercel/next.js/discussions/42301 isn't promising, and https://twitter.com/sebmarkbage/status/1587615484870098945 explicitly suggests you might need prop drilling. I'm really sad that tree-specific…
    comment by btown · 2023-09-01 · in Things I wish I knew before moving 50K lines of code to React Server Components
  28. …fashion instead of using the built-in config, something that I've been advocating for a long time ( https://github.com/vercel/next.js/discussions/17631#discussi... ). Gaeron example or the comments below show how to handle dynamic routes…
    comment by eric-burel · 2023-07-15 · in The theory versus the practice of “static websites”
  29. …complaining about this, but no feedback from the maintainers whether this is planned to bring back: https://github.com/vercel/next.js/discussions/48110
    comment by littlecranky67 · 2023-07-15 · in The theory versus the practice of “static websites”
  30. …for a bug in next.js at the moment where 404 does not return 404, that has been open for months ( https://github.com/vercel/next.js/issues/51021 ). I don't have the time of writing a PR, but I have written countless PRs and bug-reports and…
    comment by fzeindl · 2023-07-06 · in Rejected GitHub profile achievements
  31. ▲ 1
    Is server component default always a performance win? Or should it be opt-in?
    story by llwu · 2023-07-03 · 0 comments
  32. …learn Remix instead. Their official documentation for early loading scripts simply doesn’t work. https://github.com/vercel/next.js/issues/51242 Did any of this stuff get tested at all before being labeled production ready?
    comment by ecf · 2023-06-26 · in Next.js is the most frustrating, opinionated mess I've ever had to deal with
  33. …would greatly appreciate it if the Next.js team could investigate this matter (see my comment here: https://github.com/vercel/next.js/issues/49929#issuecomment-... ). As it stands, this issue is preventing me from adopting App Router for…
    comment by hampus · 2023-06-23 · in Next.js App Router Update
  34. …a currently active route in a navbar. Literally a basic building block of web applications: https://github.com/vercel/next.js/issues/43704
    comment by scientaster2 · 2023-06-06 · in Is React Having an Angular.js Moment?
  35. …- Could you give balazsorban44 bigger team? Next-Auth needs more love to be a great product. - [1] https://github.com/vercel/next.js/issues/38273
    comment by huksley · 2023-04-10 · in We Need To Talk About Vercel
  36. …are stuck using their hosting. Here’s one of the most PR-shameful threads I’ve ever read in OSS: https://github.com/vercel/next.js/discussions/19065
    comment by Kevcmk · 2023-04-10 · in We Need To Talk About Vercel
  37. …own wrapper around SWC, and also vendors it. I think it's probably the largest consumer of SWC: - https://github.com/vercel/next.js/tree/canary/packages/next-... Those add up pretty fast: - https://npmtrends.com/@next/swc-linux-x64-gnu-vs-@…
    comment by acemarke · 2023-03-07 · in Rust Is the Future of JavaScript Infrastructure (2021)
  38. Sure. 1. Last paragraph of that link you posted 2. https://github.com/vercel/next.js/issues/8851 3. https://github.com/vercel/next.js/issues/10713 4. Many similar discussions to this one here on hackernews.
    comment by 0xblinq · 2022-11-01 · in Is Turbopack really 10x faster than Vite?
  39. …says "from your machine". An issue was crated about it but they just closed without responding: https://github.com/vercel/next.js/issues/31360
    comment by hu3 · 2022-11-01 · in Is Turbopack really 10x faster than Vite?
  40. Why not both: https://github.com/vercel/next.js/tree/canary/examples
    comment by gherkinnn · 2022-10-25 · in Next.js 13
  41. …like setting up SSR by hand, you can also just use Next.js which works fine with Preact [1]. [1] https://github.com/vercel/next.js/tree/canary/examples/using...
    comment by ksbrooksjr · 2022-10-16 · in Moving from React to htmx
  42. …up third party services or components. Or check out next.js issue search for "window undefined" - https://github.com/vercel/next.js/search?q=window+undefined&... -> 1667 issues right now. Even if you discount 3/4 of those as duplicates,…
    comment by rsanheim · 2022-09-26 · in Deployment and infrastructure for a bootstrapped webapp with 150k monthly visits
  43. It has been fixed in the canary version already. Nice. https://github.com/vercel/next.js/pull/36436
    comment by quickthrower2 · 2022-08-24 · in Color has been disappearing from the world
  44. I use Zustand with Next.js. What is the issue? There are even officially maintained examples by Next: https://github.com/vercel/next.js/tree/canary/examples/with-... And Jotai: https://github.com/vercel/next.js/tree/canary/examples/with-...
    comment by chrisco255 · 2022-07-02 · in The new wave of React state management
  45. …occasional updates about the SaaS I operate. Built with Vercel's Next.js TypeScript blog example: https://github.com/vercel/next.js/tree/canary/examples/blog-...
    comment by rozenmd · 2022-06-08 · in Ask HN: Share Your Personal Site
  46. …in the documentation (getLayout as a function), which could be fixed by using a pure JSX approach: https://github.com/vercel/next.js/issues/36029
    comment by dalmo3 · 2022-05-24 · in Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
  47. …across environments and properly inline environment variables. There's a discussion about this; https://github.com/vercel/next.js/discussions/24010
    comment by GeertJohan · 2022-05-24 · in Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
  48. …and `page.js`. We are open to other opinions here, though. Others have shared similar sentiment: https://github.com/vercel/next.js/discussions/37136
    comment by leerob · 2022-05-23 · in Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
  49. Next.js Layouts RFC Discussion is Here > https://github.com/vercel/next.js/discussions/37136
    comment by ElijahLynn · 2022-05-23 · in Next.js Layouts RFC: Nested routes and layouts, designed for Server Components
  50. Will there ever be a fix or blessed workaround re: #32216? https://github.com/vercel/next.js/discussions/32216 previously: https://github.com/vercel/next.js/issues/2581
    comment by michaelsbradley · 2022-05-23 · in Next.js Layouts RFC: Nested routes and layouts, designed for Server Components