Yes. SWC is being used by Next.js to replace Babel. With SWC, compilation is about 17x faster than Babel in v12[1]. We created a CSS parser in Rust (through SWC), as well as ported many of the common Babel plugins to Rust[2]. Work is still ongoing here[3].
[1]: https://nextjs.org/blog/next-12#faster-builds-and-fast-refre...
[2]: https://nextjs.org/docs/advanced-features/compiler
[3]: https://github.com/vercel/next.js/discussions/30174
In Speedy Web Compiler – a fast TypeScript/JavaScript compilervercel
next.js
JavaScript2016–2026
vercel / next.js
next.js
The React Framework
165Distinct people
198Mentions
3Explicit recommenders
143.5KGitHub stars
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
- react/create-react-app · linked in 4 of the same discussions
- gatsbyjs/gatsby · linked in 2 of the same 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, 7:02:26 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.
* 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
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 19 | 2 | 17 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 14 | 1 | 13 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 18 | 2 | 16 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 29 | 3 | 26 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 19 | 3 | 16 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 29 | 3 | 26 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 13 | 1 | 12 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 38 | 8 | 30 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 8 | 3 | 5 |
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 GitHubWhat Hacker News says
29 sourcesI've always been a bit apprehensive of Tailwind but with the latest JIT compiler it actually seems usable. I'm happy to see it getting more use for mainstream applications but I wish it wasn't the "default" for a lot of open source projects.
For example, several of the next.js examples[1] use tailwind without explicitly stating so, because I guess it's just become a ubiquitous as css stylesheets or modules for some people. The problem I find is that it adds opinion and mental overhead for people learning related technologies or trying to get a head start without an opinionated styling solution. In order to use something like the blog-starter example for next.js I have to go and learn tailwind and then come back before I can use their blog starter, where as CSS is universal. CSS works with every project, without depending on Tailwind.
Anyw
Read the rest
ay, looking forward to seeing newer improvements to Tailwind, but I hope that people will consider it an alternative to something like Bootstrap instead of an alternative to CSS.
[1] https://github.com/vercel/next.js/tree/canary/examples/blog-...
Don't know specific growth numbers, but vercel is winning a lot of mindshare in frontend land
see nextjs repo: https://github.com/vercel/next.js/
and for frontend infra, vercel is a pretty great developer experience. Just hookup your github repo and on commit its deployed, behind CDN, preview branch URLs, etc
In Vercel raises $150M Series DThere's many reasons to have a JS compilation step:
- Still targeting legacy browsers like IE11
- Using React / JSX syntax
- Using TypeScript
- Using other brand-new JS syntax that hasn't trickled out to wider support yet
- Using custom JS transforms for libraries like `styled-components` (see this Next.js discussion thread for examples of the many different non-standard Babel transformations that people are using: https://github.com/vercel/next.js/discussions/30174 )
That said, the ideal target language version _is_ getting better. Jason Miller ( creator of Preact) has done a lot of research on both browser support for ES2017, as well as tooling to reverse-compile ES5-targeted published libraries upwards to ES2017 syntax again for improved bundle size:
- https://jasonformat.com/enabling-modern-js-on-npm/
- https://web.dev/publish-modern-
Read the rest
Ask HN: What libraries do you recommend for a Node.js CRUD web app?
Asked this here: https://github.com/vercel/next.js/discussions/30856
;TLDR What libraries do you recommend for a CRUD web app with react front end, graphql api layer and postgresql database?
My discovery so far,
Frontend: next.js
API: graphql: next.js + Apollo server
Auth: next.js auth
DB Access: Prisma or Hasura
Every year I try to learn/build something new during holiday off, This year I want to build a full stack web app in JS. For past 15+ years, I have shipped and maintained large and small web apps mostly using REST, C#, ASP.NET Core, JavaScript and react. I am familiar/dabbled with JS ecosystem and libraries but never built anything production grade in full stack JS.
I want to build an todo app with auth, user roles and permissions, graphql to fetch and mutate data in postgresql db.
What libraries you would recommend that are good,
Read the rest
stable, battle tested and would be around for few more years ?
Thank you.
Asked this question here: https://github.com/vercel/next.js/discussions/30856
;TLDR What libraries do you recommend for a CRUD web app with react front end, graphql api layer and postgresql database?
My discovery so far,
Frontend: next.js
API: graphql: next.js + Apollo server
Auth: next.js auth
DB Access: Prisma or Hasura
Every year I try to learn/build something new during holiday off, This year I want to build a full stack web app in JS. For past 15+ years, I have shipped and maintained large and small web apps mostly using REST, C#, ASP.NET Core, JavaScript and react. I am familiar/dabbled with JS ecosystem and libraries but never built anything production grade in full stack JS.
I want to build an todo app with auth, user roles and permissions, graphql to fetch and mutate data in postgresql db.
What libraries you would recommend that
Read the rest
are good, stable, battle tested and would be around for few more years ?
Thank you.
What libraries do you recommend for a Node.js CRUD web app?
1 points · Open discussionThis was not our experience earlier this year. We experienced a sequence of breaking changes in various dot-releases that led us to not being able to upgrade from 10.0.6 until 11.0.1 came out. Basically every single release in the 10.1.x and 10.2.x lines were unusable for us. We're very cautious about upgrading now.
It's part of why I suggested this issue:
https://github.com/vercel/next.js/issues/26827
In Next.js 12The imperative phrase is
> when exporting a static site
i.e. running `next export` to generate a bunch of HTML, JS and CSS files that you just serve from a static file server. It would be nice if that could generate responsive versions of your images too.
See for the feature request: https://github.com/vercel/next.js/discussions/19065
In Next.js 12Also excited about the Rust compiler! Apologies if this is far from reality, but by looking at recent commits in GH[1] it looks as though this has been rushed for a v12 release, so I was wondering how much of internal testing has this been going through before pushing it to the broader public.
[1] https://github.com/vercel/next.js/commits/canary
In Next.js 12How about on demand page revalidation* ? I can't find if it's part of Next 12.
* https://github.com/vercel/next.js/discussions/11552#discussi...
In Next.js 12It could be argued that Vite is zero config because it allows you to go without a configuration file, but it says "zero config" nowhere on the site. It isn't because I want there to always be some configuration that I avoid zero config, it's because I've seen some projects like Next.js reject requests for a configuration setting that I thought were good and it has turned me off to the idea of "zero config". https://github.com/vercel/next.js/issues/7315 https://github.com/vercel/next.js/issues/1109 https://github.com/vercel/next.js/issues/13268
In Parcel v2We've landed the TS improvments you're looking for!
https://github.com/vercel/next.js/pull/26456
In Migrating to Next.js from Create React AppNot OP but since you're asking: next/image was unusable last time I tried it. I ended up using next-optimized-images, which didn't feel a lot better but was at least usable for my case. I wanted to compile the images at build time instead.
While I'm at it, next/link also had some bonkers defaults such as the link prefetching on view instead of on hover (neither of which could be disabled, either…).
I hope all that is getting some attention soon. If I can offer some frank feedback: I've had an overall positive experience with the framework, but there have been clear quality issues here and there and I'm always concerned when I see a large feature churn without a high amount of attention being put into existing bugs.
I filed three bugs while porting an app over half a year ago (https://github.com/vercel/next.js/issues/20984, https://github.
Read the rest
com/vercel/next.js/issues/21474, https://github.com/vercel/next.js/issues/21461). None of them have even been acknowledged by a dev yet. (That last one was a doozy, too; I'm not actually sure it's a nextjs bug)
Showing the 15 most recent of 29 sources. Enable JavaScript to search and browse every indexed mention.