Thu. Dec 5th, 2019

Coding Is Future

Read the best technology articles

What is Next.js and Server-Side-Rendering?

3 min read

Next.js is a popular and lightweight framework for developing static and server-side-rendered applications with React. It already includes styling and routing solutions, and assumes that you are using Node.js as the server environment.

If you choose to do this configuration (Server-Side-Rendering) yourself, you will have to do some work and it will vary according to experience, but a painful process will be waiting for those who have no experience. Next.js is the ideal tool to save time.

Next.js works, and as a framework in a stable state, it makes the application ready to run on the server-side. I’m going to introduce you simply without going through too much technique.


Next.js wants you to obey them by creating some rules about your directory structure and how you configure your components to build your applications.

While this may seem horrible at first, it actually helps to structure your application in architecture. Next, which defines itself as Framework, can be considered as a Boilerplate like CRA.

What are the differences between client-side rendering and server-side rendering?

Server-side rendering: The content is rendered on the server, so our crawler downloads a page with HTML content already created. Due to this difference, the first screen display is faster.

Client-side rendering: Normally when using React, our crawler downloads at least one HTML page and then the content is filled with JavaScript. While this JavaScript is running we encounter a white page. After the JavaScript works, our application is ready to use.

Why We Should Choose Next.js?

  • Easy to Use: Forget about dealing with Webpack configurations, React-router, React and React-dom. Next provides you with most of the things they have to offer.
  • No need to deal with code splitting. It comes automatically.
  • First page loads are faster in performance.
  • Solves all SEO related problems.

Features Coming with Next.js

I mentioned that there is no need to deal with configurations to get started. Of course, we’re going to need some additional things when we’re drawing our own path, and we’re going to get involved in the configuration. But in the first stage, Next.js comes with many features. It also allows you to customize this structure, which comes with Babel and Webpack, with the next.config.js file.

  • Automatic code splitting
  • Built-in CSS support (styled-jsx)
  • Css-in-JS (Styled components, Glamor, Glamorous, Stlentron)
  • Static file serving
  • Routing
  • Custom server and routing
  • Prefetching Pages
  • Dynamic Import
  • Custom error handling
  • Custom configuration (webpack, babel)
  • Static HTML export

Leave a Reply