---
title: "Discussion on \"Next.js Explained: Why It Became the Default React Framework\" | Hashnode"
description: "Discussion on \"Next.js Explained: Why It Became the Default React Framework\". Why Next.js Exists\nA typical \"React-only\" app is built with a tool like Vite: it ships one nearly-empty HTML page, and a big bundle of JavaScript that builds the entire UI in the browser. That approac"
url: "https://hashnode.com/posts/next-js-explained-why-it-became-the-default-react-framework/6a4ca2015bf583a18c79b35d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Next.js Explained: Why It Became the Default React Framework](https://saurabh-ravte.hashnode.dev/next-js-explained-why-it-became-the-default-react-framework?utm_source=hashnode&utm_medium=feed)

Why Next.js Exists A typical "React-only" app is built with a tool like Vite: it ships one nearly-empty HTML page, and a big bundle of JavaScript that builds the entire UI in the browser. That approac

Jul 7 · 7 min read · saurabh-ravte.hashnode.dev  
Read the article

## Written by

[Saurabh Ravte](https://hashnode.com/@saurabhravte)

@saurabhravte · https://localhost:india

  
[View profile](https://hashnode.com/@saurabhravte)

developer

Learning, Building and writing bugs peacfully

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
