This question includes the commercial as well as open source offerings of Next Js &#x2F; Vercel.

Ask HN: What Will the Next Competitor to NextJS Be?

Show HN: Env Validator (NextJS and SvelteKit)

For some reason, embedding a Jupyter notebook in a documentation site still means doing one of these: screenshot every cell, run nbconvert and clean up the HTML, copy-paste the code into fenced blocks (losing the output), or iframe in nbviewer. Every time you update the notebook, you redo the whole dance.notebook-mdx lets you just link the `.ipynb` file and it renders inline in your MDX. No export step, no cleanup, no re-pasting. Update the notebook, rebuild the docs, done.<pre><code> :::notebook{file=&quot;.&#x2F;analysis.ipynb&quot;}
 :::
</code></pre>
That&#x27;s the API just link the file. You get authentic Jupyter styling (In&#x2F;Out prompts, syntax highlighting, rich outputs including images and HTML), build-time rendering so there&#x27;s zero client-side JS, multi-language support (Python, R, JS, SQL). Works with Next.js, Docusaurus, Fumadocs, and any MDX framework.Example output:- Example 1: <a href="https:&#x2F;&#x2F;notebook-mdx.vercel.app&#x2F;docs&#x2F;examples&#x2F;notebook-demo" rel="nofollow">https:&#x2F;&#x2F;notebook-mdx.vercel.app&#x2F;docs&#x2F;examples&#x2F;notebook-demo</a>- Example 2: <a href="https:&#x2F;&#x2F;notebook-mdx.vercel.app&#x2F;docs&#x2F;examples&#x2F;directive-example" rel="nofollow">https:&#x2F;&#x2F;notebook-mdx.vercel.app&#x2F;docs&#x2F;examples&#x2F;directive-exam...</a>Repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;abhay-ramesh&#x2F;notebook-mdx" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;abhay-ramesh&#x2F;notebook-mdx</a>Docs: <a href="https:&#x2F;&#x2F;notebook-mdx.vercel.app" rel="nofollow">https:&#x2F;&#x2F;notebook-mdx.vercel.app</a>

Show HN: Embed Jupyter Notebooks in NextJS/Docusaurus/Fumadocs Docs

Hi, I&#x27;m Andrew, a long-time hacker about to turn 50 in a few days. Today I&#x27;d like to tell you how taout.tv came into my life. It stands for &quot;talk it out&quot; and I&#x27;m told this is a &quot;portmanteau&quot; when you push two words together like brunch or smog. I met Greg at a Los Angeles tech networking group and he told me the idea.His pitch was &quot;I&#x27;ve literally heard Joe Rogan explain my product. Two people can&#x27;t agree on a subject, both think they are right. They should just talk it out.&quot; I agreed to a two-week trial as his CTO. He had been working on this for 2 years with an off-shore team. They picked nextjs for web frontend and backend, react native for ios and android, elasticsearch, redis, and postgres. Hosted on 8 digital ocean droplets and using 100ms.live for the live broadcast rooms.I was able to get the droplet count (and size) down to just 2, using only postgres (pgvector search), frontend web is just js react no nextjs. Backend is now all golang. And the two mobile apps are native swift and kotlin.There&#x27;s actually a lot to this platform. If you are familiar with orgs like bridgeusa.org or braverangels.org this idea of bridging people on two different sides is something a lot of people care about. You schedule a podcast with someone you already know, or you can just post your desire to talk about a subject with anyone. You and your co-host go live and the audience can watch and score each side in real time. You can upload evidence to support your side and all these scores are tracked and recorded.Would love some feedback from users with podcasting experience.<a href="https:&#x2F;&#x2F;www.taout.tv&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.taout.tv&#x2F;</a>Thanks!

Show HN: Bridging People Together via Podcasts

You&#x27;re right — corrected: <a href="https:&#x2F;&#x2F;finterm.xyz&#x2F;blog&#x2F;nextjs-on-cloudflare-workers" rel="nofollow">https:&#x2F;&#x2F;finterm.xyz&#x2F;blog&#x2F;nextjs-on-cloudflare-workers</a>.Argon2id was my choice eventually for OWASP reasonsOn-by-default nodejs_compat would be welcome - Thanks!

What breaks when you ship Next.js on Cloudflare Workers

Currently Working on <a href="https:&#x2F;&#x2F;devlens.io" rel="nofollow">https:&#x2F;&#x2F;devlens.io</a> which is an Open source Intelligent Codebase Visualizer for javascript, Reactjs, nextjs and nodejs for easy onboarding and easy PR review.
The open source version is live at <a href="https:&#x2F;&#x2F;github.com&#x2F;devlensio&#x2F;devlensOSS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;devlensio&#x2F;devlensOSS</a>You can star the repo if you like the project. I am still working on cloud version which will have lots of features.Also the main MOAT of Devlens is not the visualizer but the blast radius feature. Which essentially tells you if I change this file&#x2F;function where it will affect my Codebase which is specially useful for PR review.

Ask HN: What are you working on (non-AI)?

Currently Working on <a href="https:&#x2F;&#x2F;devlens.io" rel="nofollow">https:&#x2F;&#x2F;devlens.io</a> which is an Open source Intelligent Codebase Visualizer for javascript, Reactjs, nextjs and nodejs for easy onboarding and easy PR review.The open source version is live at <a href="https:&#x2F;&#x2F;github.com&#x2F;devlensio&#x2F;devlensOSS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;devlensio&#x2F;devlensOSS</a>You can star the repo if you like the project. 
I am still working on cloud version which will have lots of features.

I bought into the end 2 end typesafety + everything is written in TypeScript hype and it did allow us to build a large portion of our application fairly quickly. Again, it&#x27;s the 90% that work great this way and I don&#x27;t think other batteries included frameworks would have saved us. I would also say that complexity in our case leans more on the frontend so having a more batteries included backend would not have been that helpful.What I will say though is that if I could go back I would probably reconsider the &quot;everything in typescript&quot; and &quot;lets use nextjs, it&#x27;s what everybody uses&quot; and reach for something more performant because the things that turned out to be difficult to build cleanly again existed on the edges of all of this.Perhaps Go or Rust for the backend, generate a client or bindings and Solid or Svelte for the frontend.

The Modern React Stack Explained for 2026

For the past two years I have worked on a SaaS platform for the education space that we are about to launch (small 2 person start up) - it involves a lot of highly dynamic forms and fairly complex client side state and tons of rather complex components and workflows.The stack for non-specifics we landed on for now coincides with a lot of what is mentioned in the blog post with a few extras:Nextjs, oRPC, Next-Intl, Zod, Tanstack Form, Tanstack Query, Drizzle, SQLite, Tiptap, Better-Auth, Jest, Tailwind, a heavily customized Shadcn.However there are a few more things I would like to mention.Formatting: OxfmtLinting: OxlintE-Mails: react-emailIcon Library: LucideUser HTML in React: InterweaveDate Handling: date-fnsDrag and Drop Handling: DnD KitPayment (MoR): Creem (we are EU based, so a EU MoR matters to us)The blog post creates a good overview of technologies that exist out and some pros and cons but it&#x27;s not so clear to me why the things that are recommended are recommended except for: Companies use them.We went through multiple rewrites of large parts of the codebase, originally we started out using supabase for the backend, then moving to drizzle with self hosted postgres, then switching to sqlite. We started with react-hook-form and switched to Tanstack Form. We had our own UI library, then switched to Shadcn and customized that heavily. We used next-auth (now auth.js) and switched to better-auth, used server actions, then switched to oRPC.Most of the decisions we made were either grounded in a very specific technical aspect related to our product or just out of curiousity of whether the grass would be greener on the other side (it was sometimes, not always).In my normal day job I have also mostly worked on Nextjs apps for the past few years, eCommerce, internal dashboards and tools etc and I guess my takeaway is that most of these tools can get you where you want but depending on the shape of your problem(s), some lend themselves better than others and you will probably only find out if you try it out. If you are building a highly complex app, you will inevitably run into situations where all those libraries and frameworks will not provide you with the things you want or will expose primitives that make it cumbersome to work with. I will give one recent example:In our application we worry a lot about potential loss of form data of dynamically created forms, so we need some sync solution for said form data and have some form of persistence. The all-encompassing solution for us would involve: Local sync to indexed db, including tab sync, websocket sync of change increments (not the entire form, they are quite large), retry on error &#x2F; connection loss, ideally some state merging logic for the form state in case of divergence with last writer wins fallback, granular form validation with different representations of data for draft and submit states, atomic re-renders (e.g. save button gets disabled when sync is in flight but no full re-renders when the form object changes) and different representations of the form data (image URLs from the server snapshot look different than base64 representations in the form for example). This is not trivial. We looked at different LoFi solutions (Tinybase, different CRDT approaches, Zero, SignalDB) with SignalDB being the closest one to what we would like. Eventually we had to ditch that too and implement a lesser version of all of this for our v1 that syncs the entire exam state periodically over oRPC (+ debounced local storage) and a pretty massive hook that abstracts the sync logic over various forms and form builders we have to handle all sorts of edge cases. Tanstack form is not meant for this (dirty tracking does not line up if the &quot;default state&quot; changes), there is no concept of drafts and final forms, there are no storage adapters that do conflict resolution the way you might want because that is so specific to your app.Another point I would like to make is that, while modern react stacks do afford the developer a pretty nice UX 90% of the time, sometimes that comes with some pretty annoying tradeoffs. Nextjs is quite heavy and slow. No cron jobs when self-hosting. Having your db schema defined in TS (using drizzle), tacking some extra Zod on it at the client&#x2F;server boundary and carry it through into the frontend and eventually in Tanstack form is very nice on paper but for dynamic forms with arrays and more complex data types the TypeScript LSP will absolutely shit the bed, even TSGO can&#x27;t keep up or outright crashes regularly for me. Tanstack form type inference for form fields is also lacking for complex array types for us. Using SQLite is great because no separate process is needed to host the DB, but you don&#x27;t get CDC or realtime updates easily (maybe turso will help here in the future).
Using shadcn is really cool to get up and running and build things that look generally professional and nice, but once you modify the files (which you will need to in order to keep up with the demands of the app) the upgrade path becomes painful and the shadcn dependency list and amount of DOM it sometimes produces of it is also ridiculous.All that is to say, I think the difficult part of engineering even in 2026 happens at the outer edges of what you build and no framework or stack is gonna save you from all of that (and probably shouldn&#x27;t!).

React Query I&#x27;ve managed to avoid but it&#x27;s really a cache + promise hook, it&#x27;s fairly versatile.Tanstack Start &#x2F; Router are pretty great coming from nextjs, and not limited to React either.

Postmortem: TanStack NPM supply-chain compromise

&gt; how to start a projectThis is a weird thing to point out. I&#x27;ve always had to look up how to start a project even before LLMs, even with years of experience. With React there&#x27;s vite, React router, nextjs, tanstack. With nodejs there&#x27;s Koa, hapi, express, and tons others.Most fullstack engineers are likely not starting a lot of new projects at work, and may only be doing it a few times for side projects, LLM or no.

I'm going back to writing code by hand

If you&#x27;re using GenAI, you should go through the process of selecting an optimal tech stack for each solution, but also take into consideration that Claude and other services probably the most knowledge of python, javascript, and typescript with go, rust, java, and c# following closely behind. Consider what you&#x27;re building and what elements of the tech stack is optimal for your problem-space.I don&#x27;t know rust at all and I&#x27;ve built three applications using it with Claude because it has speed and correctness built-in.I use Typescript for 90% of the things I build. For web development I&#x27;ve used a number of tools, but mostly react, nextjs, or raw html&#x2F;css&#x2F;js. But if I were building an enterprise application I&#x27;d consider my team and whether opinionated (Angular) was optimal over flexible (React).Each project should consider its own optimal tech stack.

If AI writes your code, why use Python?

I wonder though, can AI make the next JS framework. I mean that in sincerity, there was the leap from jQuery to React for ex. If an AI only knows jQuery and no one makes React, will React come out of AI.

Software engineering may no longer be a lifetime career

Location: Poland,
 Remote: Only
 Willing to relocate: No
 Technologies: Javascript, Typescript, PostgreSQL, MongoDB, React, Svelte, Sveltekit, NextJS, XState, Redux, GCP, DO, Railway, Vercelgenerally speaking im tool agnostic as long as its in Javascript&#x2F;Typescript however i also have some experience working in golang and python.Résumé&#x2F;CV: <a href="https:&#x2F;&#x2F;drive.google.com&#x2F;file&#x2F;d&#x2F;1tRM1IUTSCK-NQNn_1mFf8_cv9rf9KOQy" rel="nofollow">https:&#x2F;&#x2F;drive.google.com&#x2F;file&#x2F;d&#x2F;1tRM1IUTSCK-NQNn_1mFf8_cv9rf...</a>Email: martinxy80@gmail.comI have been building my own product, in MVP stage but run out of time to secure funding it&#x27;s currently used in a school.

Ask HN: Who wants to be hired? (May 2026)

it does, it&#x27;s a nextjs app so there&#x27;s a bunch of top level pages that work as you&#x27;d expect. The issue is that we&#x27;re trying to be a real company, those pages have nested logic, multiple views, sub navigation, search, filtering, wizards, all of which are in a cascade of react hooks because AI is obsessed with self-contained hooks. none of that state is linkable.What i learned, by fire, is that nextjs works well with its nested routing and layout-to-hold-context magic. it&#x27;s quite nifty but it&#x27;s not free and not obvious, you have to design for it. I can&#x27;t state enough that AI will ship a billion hooks, it loves hooks for self-contained state. My colleague made a good point that that style is a feature; it limits blast radius of N features all building on top of each other.Yeah i had to move on from there.

Using Claude Code: The unreasonable effectiveness of HTML

I&#x27;m a ML Engineer with a year of experience in delivering fast agentic pipelines and AI solutions to clients all around the world, feel free to check my website! <a href="https:&#x2F;&#x2F;kev187038.github.io" rel="nofollow">https:&#x2F;&#x2F;kev187038.github.io</a>Location: CyprusRemote: yesWilling to relocate: NoTechnologies: RAG, Agentic AI Pydantic, Langfuse, LangChain, Vercel, Railway, Hatchet, FastAPI, NextJS, React and more on my websitelinkedin: <a href="https:&#x2F;&#x2F;linkedin.com&#x2F;in&#x2F;gabriele-matini" rel="nofollow">https:&#x2F;&#x2F;linkedin.com&#x2F;in&#x2F;gabriele-matini</a>website: <a href="https:&#x2F;&#x2F;kev187038.github.io" rel="nofollow">https:&#x2F;&#x2F;kev187038.github.io</a>Resume: <a href="https:&#x2F;&#x2F;drive.google.com&#x2F;file&#x2F;d&#x2F;1nxKtxDy53eBWIBDkbCrqVbnZbwQsV9dT&#x2F;view?usp=sharing" rel="nofollow">https:&#x2F;&#x2F;drive.google.com&#x2F;file&#x2F;d&#x2F;1nxKtxDy53eBWIBDkbCrqVbnZbwQ...</a>Email: gabriele.matini18@gmail.comgithub: <a href="https:&#x2F;&#x2F;github.com&#x2F;kev187038" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;kev187038</a>Industries I am not willing to work in: adult entertainment, gamblingBuild robust, ship fast!

Web technologies got so many things right. People complain about it so much but it&#x27;s amazing.I worked with a vibe coded app at my last job (and since quit due to it) and because it was a nextjs SPA frontend with a separate API backend, the user facing urls didn&#x27;t match the backend endpoints. Because AI uses react hooks for everything, state is in-memory, url-based routing isn&#x27;t a thing unless you design for it. So links aren&#x27;t free and thus we have no way for users to link to anything other than top-level entry points. LINKS! Especially for internal tools, everything being linkable is vital to collaboration and problem solving.The need for uniform resource locations and verbs was so well thought out, 30 or 40 some odd years ago.

hi everyone,just released an interview i did with tanner linsley, creator of tanstackwe discussed tanstack start, tanstack vs next.js, why next js can feel too magical, react server components, typescript inference, whether tanstack could ever become something like laravel or rails, and morewould love to hear what you think

[dead]

Gridmatic | Product engineer + data engineer | 175-235k + equity | Cupertino, CA (hybrid)Hi HN! We’re an energy + AI startup that applies modern deep learning and optimization to improve the use of renewables and grid-scale batteries to deliver cheap, clean energy to commercial&#x2F;industrial customers. We also do energy trading and battery optimization.Roles:- Data engineer: we&#x27;re hiring our first data eng! Looking for a startup-minded SWE to work on both ingest and transformation of datasets that power our best-in-class ML models for energy forecasting.- Product engineer: our energy sales have been growing rapidly and we want to 10x it from here, which involves building a lot of tooling to make sales more automated. This tends to be backend&#x2F;data heavy, but will also have some frontend (NextJS&#x2F;React&#x2F;Typescript).If you&#x27;re interested in making a real-world impact on climate&#x2F;energy, or if you know someone that might, please email me and include a one sentence description of the most impressive thing you&#x27;ve built: kevin@gridmatic.com

Ask HN: Who is hiring? (May 2026)

While you are dying on a hill, with the help of LLMs, I&#x27;m shipping quality software and features to my customers at a pace I haven&#x27;t been able to before. And no, not some nextjs slop. If you are letting your LLM look at StackOverflow, you are doing it wrong - it needs to be grounding in your stacks official docs and any other style&#x2F;rules you prefer wired with other tooling like linting&#x2F;formatting, duplication checking, etc. And yes, you have to constantly monitor the output and review every line of code - but it&#x27;s still faster and if managed correctly, produces better code and (this is the hill I will die on) better test suites and documentation than I would have written.

Vibe coding and agentic engineering are getting closer than I'd like

# This is a NextJS
NextJS is a **framework for ReactJS**.

Wait a second ... a "framework" for React? Isn't React itself already a framework for JavaScript?

Well ... first of all, React is a "library" for JavaScript. That seems to be important for some people.

Not for me, but still, there is a valid point: React already is a framework / library for JavaScript. So it's already an extra layer on top of JS.

## Getting Started

Create Next App:

```bash
npx create-next-app
# or
yarn create next-app
```

First, run the development server:

```bash
npm run dev
# or
yarn dev
```

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.

You can start editing the page by modifying `pages/index.js`. The page auto-updates as you edit the file.

[API routes](https://nextjs.org/docs/api-routes/introduction) can be accessed on [http://localhost:3000/api/hello](http://localhost:3000/api/hello). This endpoint can be edited in `pages/api/hello.js`.

The `pages/api` directory is mapped to `/api/*`. Files in this directory are treated as [API routes](https://nextjs.org/docs/api-routes/introduction) instead of React pages.

## Why would we then need NextJS?

Because NextJS makes building React apps easier - especially React apps that should have server-side rendering (though it does way more than just take care of that).

In this article, we'll dive into the core concepts and features NextJS has to offer:

- File-based Routing
- Built-in Page Pre-rendering
- Rich Data Fetching Capabilities
- Image Optimization
- Much More

## File-based Routing

![Create routes via your file + folder structure](nextjs-file-based-routing.png)

# File-based Routing In Action

![Create routes via your file + folder structure](nextjs-file-based-routing-in-action.png)

## Learn More

To learn more about Next.js, take a look at the following resources:

- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.

You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!

## Deploy on Vercel

The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.

Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.

... More content comming soon ...

NextJs News

News From: hn.algolia.com

Ask HN: What Will the Next Competitor to NextJS Be?

Show HN: Env Validator (NextJS and SvelteKit)

Show HN: Embed Jupyter Notebooks in NextJS/Docusaurus/Fumadocs Docs

Show HN: Bridging People Together via Podcasts