HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vercel
next.js
JavaScript2016–2026
vercel / next.js

next.js

The React Framework

Web DevelopmentSystems & InfrastructureLanguages & CompilersCreative & Media
Explore on GitHubRead Hacker News discussions
165Distinct people
198Mentions
3Explicit recommenders
143.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The React Framework

GitHub

Where it is used

  • Vercel — “If you already have a project with Next.js, install Vercel CLI and run the vercel command from your project's root directory” Source
  • Plex — Plex uses Next.js to power their web experiences with SSR, on-demand ISR, and Edge Middleware. This helped improve search ranking and traffic after their relaunch. Source

What people are saying

> You don't think you're maybe contorting yourself to make some of these arguments work? First of all, I still prefer TypeScript to Python when it comes to language features.…

spion used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:01:28 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year198 dated mentions

Observed mentions: 2016-10-25 16:05:56 UTC to 2026-05-15 16:42:15 UTC.

0102030402016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 19 mentions; 2 submissions, 17 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 14 mentions; 1 submissions, 13 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 18 mentions; 2 submissions, 16 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 29 mentions; 3 submissions, 26 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 19 mentions; 3 submissions, 16 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 29 mentions; 3 submissions, 26 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 38 mentions; 8 submissions, 30 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC321
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC19217
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC14113
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC817
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC18216
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC29326
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC19316
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC29326
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC13112
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC38830
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC835

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Next.js Getting Started Used by some of the world's largest companies, Next.js enables you to create full-stack web applications by extending the latest React features, and integrating powerful Rust-based JavaScript tooling for the fastest builds. Visit our Learn Next.js course to get started with Next.js. Visit the Next.js Showcase to see more sites built with Next.js. Documentation Visit https://nextjs.org/docs to view the full documentation. Community The Next.js community can be found on GitHub Discussions where you can ask questions, voice ideas, and share your projects with other people. To chat with other community members, you can join the Next.js Discord server. Do note that our Code of Conduct applies to all Next.js community channels. Users are highly encouraged to read and adhere to it to avoid repercussions. Contributing Contributions to Next.js are welcome and highly appreciated. However, before you jump right into it, we would like you to review our Contribution Guidelines to make sure you have a smooth experience contributing to Next.js. Good First Issues: We have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place for newcomers and beginners alike to get started, gain experience, and get familiar with our contribution process. Security If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and NOT open a public issue. To participate in our Open Source Software Bug Bounty program, please visit https://hackerone.com/vercel.
Read the full README on GitHub

What Hacker News says

13 sources
0xblinq·Nov 24, 2024
Using Next.js for self hosting is a really bad idea in my opinion (and experience). Despite of what they say (for obvious marketing reasons) their framework is optimized and developed to run on their platform later. One of the problems people don’t seem to realize, is that when you use it on your own server you are still “paying” for the trade offs they made. Like you will run into artificial limitations that should not be there at all, except because those limitations only help keeping the door open so that you can move into their platform. If they removed those limitations then moving into their platform 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 p
Read the rest
eople realizing this. So… if you are using Vercel, then great. Next is your best option for their platform. But using Next outside of vercel is a terrible idea. There are far better options for that.
In Show HN: Self-Host Next.js in Production
novoreorx·Oct 11, 2024
I have ranted countless times in Next.js issues, and most of them have not been resolved even after 2 to 3 years. Here, I'll just 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: https://github.com/vercel/next.js/discussions/44506 - router.push does not revalidate server cache: https://github.com/vercel/next.js/discussions/54075#discussi... - stylesheet order is not guaranteed and persist accross environments: https://github.com/vercel/next.js/issues/16630 - script tag with strategy=beforeInteractive does not work in root layout: https://github.com/vercel/next.js/issues/51242 Some other thoughts: One thing Next.js likes to do is provide a lengthy and well-formatted post explaining thei
Read the rest
r philosophy and reasons why a particular issue cannot be resolved. It appears convincing at first glance, but if you take a closer look, you'll find that they are just elaborations using their own terms and logic. In other words, they explain the efforts they make to justify their decisions, which stem from poor design choices they made. They like doing things look correct but not necessarily useful, similar to the feelings I have when dealing with accountants.
In Next.js, Just Why? (2023)
throwitaway1123·Sep 26, 2024
> Look at the dependency tree for a next Looks ok to me: https://npmgraph.js.org/?q=next Ironically, most of the dependencies are actually Rust crates used by swc and turbopack [1][2]. Try running `cargo tree` on either of those crates, it's enlightening to say the least. And of course, Node has a built in file watcher, and even 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] https://npmgraph.js.org/?q=chokidar
In Rewriting Rust
sorokinvj·Jul 27, 2024
I developed my personal site - https://vladislavsorokin.com (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, especially if you copy-paste from GPT, but ideally I would like to write it on the page itself so you see immediately what you get and you don't need to run the localhost etc. I think its not really that hard to make it.
In Ask HN: What is the best way to author blogs in 2024?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.