---
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\". If React is so popular, why was Next.js created?\nReact is an excellent UI library, but it only solves one piece of the puzzle: managing component state and updating the DOM. By default, a standard Rea"
url: "https://hashnode.com/posts/next-js-explained-why-it-became-the-default-react-framework/6a89d69a3b6e24154ef43b2a"
---

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

Discussion

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

If React is so popular, why was Next.js created? React is an excellent UI library, but it only solves one piece of the puzzle: managing component state and updating the DOM. By default, a standard Rea

Aug 22 · 5 min read · swapnadip-syntexandstory.hashnode.dev  
Read the article

-   [#chai](https://hashnode.com/tag/chai)
-   [#chaicode](https://hashnode.com/tag/chaicode)
-   [#chaiaurcode](https://hashnode.com/tag/chaiaurcode)

## Written by

[Swapnadip Sahoo](https://hashnode.com/@swapnadip23)

@swapnadip23 · Pnaskura, India

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

नमस्ते

## Responses

Markdown supported · ⌘↵ to post

No responses yet.