Day 2: Basic Routing in Next.js

Welcome back to our Next.js tutorial series! Today, we will dive into the intricacies of basic routing in Next.js. Routing is a fundamental aspect of any web application, allowing users to navigate between different pages. Next.js provides a seamless and intuitive way to handle routing in your React applications.

Dynamic Routing

One of the powerful features of Next.js is its dynamic routing capability. With dynamic routing, you can create pages that are generated on-the-fly based on their URL parameters. This is particularly useful when you have pages that share the same layout but display different content, such as a blog post or a product page.

To demonstrate dynamic routing, let’s create a simple blog application with Next.js.

Step 1: Create a New Page

Inside the pages directory, create a new file called blog.js. This will be our blog page where we will display a list of blog posts.

Step 2: Set Up Routing

In the blog.js file, we need to define the necessary code to fetch and display the blog posts. We will also set up the routing for our individual blog post pages.

import React from 'react';
import Link from 'next/link';

const Blog = ({ posts }) => {
  return (
    <div>
      <h1>Blog</h1>
      <ul>
        {posts.map((post) => (
          <li key={post.id}>
            <Link href={`/blog/${post.slug}`}>
              <a>{post.title}</a>
            </Link>
          </li>
        ))}
      </ul>
    </div>
  );
};

export default Blog;

In the code above, we create a functional component called Blog that receives a list of blog posts as props. We map over the posts array and render a list item for each post. Each list item is wrapped with the Link component from Next.js, which handles the client-side navigation.

Step 3: Fetch Data

To fetch the blog posts, we can use a simple mock API. Create a new file called api/posts.js with the following content:

export const getPosts = () => {
  return [
    { id: 1, title: 'First Post', slug: 'first-post' },
    { id: 2, title: 'Second Post', slug: 'second-post' },
    { id: 3, title: 'Third Post', slug: 'third-post' },
  ];
};

This file exports a function called getPosts that returns an array of blog posts.

Step 4: Fetch Data on Page Load

To ensure the blog posts are fetched when the Blog component is rendered, we can use the getServerSideProps function from Next.js. Update the blog.js file with the following code:

import React from 'react';
import Link from 'next/link';
import { getPosts } from '../api/posts';

const Blog = ({ posts }) => {
  return (
    <div>
      <h1>Blog</h1>
      <ul>
        {posts.map((post) => (
          <li key={post.id}>
            <Link href={`/blog/${post.slug}`}>
              <a>{post.title}</a>
            </Link>
          </li>
        ))}
      </ul>
    </div>
  );
};

export const getServerSideProps = async () => {
  const posts = getPosts();

  return {
    props: {
      posts,
    },
  };
};

export default Blog;

In the updated code, we import the getPosts function from our API module and use it inside the getServerSideProps function. This function runs on the server-side and fetches the blog posts before rendering the Blog component.

Step 5: Create Individual Blog Post Pages

Now, let’s create individual pages for each blog post. Inside the pages directory, create a new folder called blog. Inside this folder, create a new file called [slug].js. This file will handle the dynamic routing for our blog post pages.

In the [slug].js file, add the following code:

import React from 'react';
import { useRouter } from 'next/router';

const BlogPost = () => {
  const router = useRouter();
  const { slug } = router.query;

  return (
    <div>
      <h1>Blog Post</h1>
      <h2>{slug}</h2>
    </div>
  );
};

export default BlogPost;

In this code, we import the useRouter hook from Next.js to access the current URL parameters. We extract the slug parameter from the router.query object and render it as the title of the blog post page.

Step 6: Test the Application

To test our application, run the development server with the npm run dev command. Visit http://localhost:3000/blog in your web browser, and you should see the list of blog posts. Clicking on a blog post title will take you to the individual blog post page.

Congratulations! You have successfully implemented basic routing in Next.js and created dynamic pages based on URL parameters. In the next tutorial, we will explore more advanced routing features and create nested routes.

Keep coding and stay tuned for Day 3! 🚀💻

#NextJS #WebDevelopment #ReactFramework

Mastering Next.js: Introduction to Next.js

Day 1: Introduction to Next.js

Welcome to the first day of our in-depth exploration of Next.js, a powerful React framework that has reshaped the landscape of web development. In this tutorial, we will unravel the intricacies of Next.js, understand its profound benefits, and guide you through setting up your inaugural Next.js project. Let’s not just scratch the surface but delve into the code to grasp the key features that make Next.js a developer’s delight.

Note: We are using Next.js 14 version in this series

Understanding Next.js

Before we delve into the code, let’s grasp the essence of Next.js. Next.js is a React framework designed to simplify the process of building robust and performant web applications. It introduces conventions and tools to streamline common tasks, making it an excellent choice for modern, server-rendered React applications.

Benefits of Next.js

1. Server-Side Rendering (SSR):

Next.js excels in server-side rendering, rendering pages on the server rather than the client. This improves initial loading speed and enhances SEO.

2. Zero Configuration:

One of Next.js’ standout features is its minimal setup requirements, allowing for quick and efficient development.

3. Automatic Code Splitting:

Next.js intelligently splits JavaScript bundles for faster page loads and a smoother user experience.

4. Hot Module Replacement (HMR):

HMR allows real-time changes without a full page reload, speeding up the development process.

5. Full TypeScript Support:

Next.js has robust TypeScript integration, providing static typing for your entire project, enhancing code quality and collaboration.

Setting Up Your First Next.js Project

Let’s jump into the code and set up your first Next.js project.

Step 1: Install Node.js and npm

Before diving into Next.js, ensure you have Node.js and npm installed on your machine. You can download them from the official Node.js website.

Step 2: Create a New Next.js Project

Open your terminal and run the following command to create a new Next.js project:

npx create-next-app@latest

Step 3: Navigate to Your Project

Change into the project directory:

cd todo-app

Step 4: Run Your Development Server

Start the development server with the following command:

npm run dev

Visit http://localhost:3000 in your web browser to see your Next.js application.

The folder structure will look like this

File structure

The key structure of next.js app is

Routing Files

File / Folder nameFile extensionDetails
layout.js .jsx .tsxLayout
page.js .jsx .tsxPage
loading.js .jsx .tsxLoading UI
not-found.js .jsx .tsxNot found UI
error.js .jsx .tsxError UI
global-error.js .jsx .tsxGlobal error UI
route.js .tsAPI endpoint
template.js .jsx .tsxRe-rendered layout
default.js .jsx .tsxParallel route fallback page

These are just top-level project structures. We will have nested levels and dynamic routing levels. We can discuss them further in subsequent posts.

The folder structure of a default Next.js 14 project is as follows:

- .next/
- components/
- node_modules/
- pages/
  - api/
  - index.js
- public/
  - favicon.ico
  - vercel.svg
- styles/
- README.md
- package-lock.json
- package.json

Here’s a brief explanation of the main folders and files:

  • .next/: This folder contains the compiled output of your Next.js project.
  • components/: This folder is where you can store reusable React components.
  • node_modules/: This folder contains the dependencies installed for your project.
  • pages/: This folder is where you define your application’s routes/pages.
    • api/: This subfolder is used for setting up API routes.
    • index.js: This is the main entry point of your Next.js application.
  • public/: This folder is used to store static files like images, fonts, and favicon.
  • styles/: This folder is where you can store your CSS or SCSS files.
  • README.md: This file typically contains information about your project.
  • package-lock.json and package.json: These two files contain the dependencies and scripts needed for your project.

Note that this is the basic structure of a Next.js project and you can add more folders and files based on your specific needs.

Conclusion

Congratulations! You’ve set up your first Next.js project and explored its file structure. As we continue this series, we’ll delve deeper into advanced topics. Stay tuned for Day 2, where we will explore the intricacies of basic routing in Next.js.

Happy coding! 🚀💻

#NextJS #WebDevelopment #ReactFramework