Build API-Only Projects with Next.js, Prisma, and Supabase

Creating an API-only project in Next.js offers the flexibility to leverage the Next.js file-based routing system, API routes, and powerful integrations such as Prisma and Supabase. This setup will allow you to manage your database, interact with it via Prisma, and handle authentication and data with Supabase Postgres.

  1. Prerequisites
  2. Setting up the Project
  3. Installing Dependencies
  4. Configuring Supabase
  5. Setting up Prisma
  6. Creating API Routes in Next.js
  7. Deploying the API
  8. Conclusion

Prerequisites

Before starting, make sure you have the necessary installed:

  • Node.js (v16+)
  • Supabase Account (for database hosting)
  • Postgres Database (via Supabase)
  • Prisma ORM

Familiarity with Next.js, Prisma, and Supabase will also help.

Setting up the Project

First, set up a new Next.js project.

npx create-next-app@latest my-api-project
cd my-api-project

Since this is an API-only project, you can safely remove the default pages/index.tsx and pages/api/hello.ts files. We’ll focus on building our API inside the pages/api directory.

Installing Dependencies

Now, install the necessary dependencies for Prisma and Supabase:

npm install @prisma/client prisma @supabase/supabase-js
  • @prisma/client: The Prisma client to query the database.
  • prisma: The Prisma toolkit for schema migrations.
  • @supabase/supabase-js: Supabase JavaScript SDK for interacting with the Supabase database.

Configuring Supabase

  1. Create a New Supabase Project: Go to the Supabase dashboard and create a new project. Note down the API link, public anon key, and the database connection string from the Settings > API section.
  2. Set Up Environment Variables: In your Next.js project, create an .env.local file to store sensitive information like the database URL and Supabase keys.
NEXT_PUBLIC_SUPABASE_URL=https://xyzcompany.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key
DATABASE_URL=postgresql://username:password@dbhost:5432/mydb
  • NEXT_PUBLIC_SUPABASE_URL: URL for your Supabase project.
  • NEXT_PUBLIC_SUPABASE_ANON_KEY: The public anonymous key for accessing Supabase from the frontend.
  • DATABASE_URL: The connection string to your Postgres database hosted on Supabase.

Setting up Prisma

  1. Initialize Prisma: Run the following command to initialize Prisma in your project.
npx prisma init

This creates a prisma folder with a schema.prisma file and updates your .env with DATABASE_URL.

  1. Update Schema: Open prisma/schema.prisma and define a model. For example:
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model User {
  id        Int      @id @default(autoincrement())
  email     String   @unique
  name      String?
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}
  1. Migrate the Database: After updating the schema, apply the changes to your Supabase database:
npx prisma migrate dev --name init

This will create a User table in your Supabase Postgres database.

  1. Generate Prisma Client: Run the following command to generate the Prisma client.
npx prisma generate

Creating API Routes in Next.js

Next.js provides a simple way to create APIs using the /pages/api directory. Let’s create a basic CRUD API for the User model.

  1. Creating a User: Inside pages/api/user/index.ts, create a POST endpoint to add a new user.
import { PrismaClient } from '@prisma/client';

const prisma = new PrismaClient();

export default async function handler(req, res) {
  if (req.method === 'POST') {
    const { email, name } = req.body;

    try {
      const user = await prisma.user.create({
        data: {
          email,
          name,
        },
      });
      res.status(201).json(user);
    } catch (error) {
      res.status(400).json({ error: 'User creation failed' });
    }
  } else {
    res.status(405).json({ message: 'Method not allowed' });
  }
}
  1. Getting All Users: To fetch all users, add a GET request handler in the same file.
if (req.method === 'GET') {
  try {
    const users = await prisma.user.findMany();
    res.status(200).json(users);
  } catch (error) {
    res.status(400).json({ error: 'Failed to fetch users' });
  }
}

Now you have both POST and GET API endpoints ready for creating and fetching users.

Deploying the API

You can deploy your Next.js API project using Vercel, the creators of Next.js. Simply push your code to a GitHub repository and connect it to Vercel.

  1. Push Code to GitHub:
   git init
   git add .
   git commit -m "Initial commit"
   git remote add origin <YOUR_GITHUB_REPO_URL>
   git push -u origin main
  1. Deploy to Vercel:
  • Sign in to Vercel and import your GitHub repository.
  • Add the necessary environment variables (NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, and DATABASE_URL).
  • Click deploy, and your API will be live.

Conclusion

In this guide, you learned how to create an API-only project in Next.js with Prisma and Supabase Postgres. This stack provides a powerful yet flexible way to build backends quickly, with an API layer built into the Next.js framework.

You can now extend this API with additional models. You can integrate authentication using Supabase’s built-in auth tools. You can also expand it with more advanced features like pagination and filtering.

Happy Coding!

Memoization for Optimal Data Fetching in Next.js

Next.js offers a powerful toolkit for building modern web applications. A crucial aspect of Next.js development is efficiently fetching data to keep your application dynamic and user-friendly. Here’s where memoization comes in – a technique that optimizes data fetching by preventing redundant network requests.

What is Memoization?

Memoization is an optimization strategy that caches the results of function calls. When a function is called with the same arguments again, the cached result is returned instead of re-executing the function. In the context of Next.js data fetching, memoization ensures that data fetched for a specific URL and request options is reused throughout your component tree, preventing unnecessary API calls.

Benefits of Memoization:

  • Enhanced Performance: By reusing cached data, memoization significantly reduces network requests, leading to faster page loads and a smoother user experience.
  • Reduced Server Load: Fewer requests to your server free up resources for other tasks, improving overall application scalability.

Understanding Memoization in Next.js Data Fetching:

React, the foundation of Next.js, employs memoization by default for data fetching within components. This applies to:

  • getStaticProps and getServerSideProps: Even though these functions run on the server, the subsequent rendering of the components on the client-side can benefit from memoization.
  • Client-side fetching with fetch or data fetching libraries: Memoization helps prevent redundant calls within the React component tree.

Real-world Example: Product Listing with Pagination

Imagine a Next.js e-commerce app with a product listing page that uses pagination for better navigation. Here’s how memoization can optimize data fetching:

// ProductList.js

import React from 'react';

function ProductList({ products }) {
  return (
    <ul>
      {products.map((product) => (
        <li key={product.id}>{product.name}</li>
      ))}
    </ul>
  );
}

export async function getStaticProps(context) {
  const page = context.params.page || 1; // handle pagination
  const response = await fetch(`https://api.example.com/products?page=${page}`);
  const products = await response.json();

  return {
    props: { products },
    revalidate: 60, // revalidate data every minute (optional)
  };
}

export default ProductList;

In this example, getStaticProps fetches product data for a specific page. Memoization ensures that if a user clicks through pagination links requesting the same page data (e.g., page=2), the data is retrieved from the cache instead of making a new API call.

Additional Considerations:

  • Memoization Limitations: Memoization only applies within the same render pass. If a component unmounts and remounts, the cache won’t be used.
  • Custom Logic for Dynamic Data: If your data fetching relies on factors beyond URL and request options (e.g., user authentication or data in the URL path), you’ll need additional logic to handle cache invalidation or data updates.

Tips for Effective Memoization:

  • Leverage Data Fetching Libraries: Libraries like SWR or React Query provide built-in memoization and caching mechanisms for data fetching, simplifying implementation.
  • Control Caching Behavior: Next.js allows you to control cache headers for specific data requests using the revalidate option in getStaticProps or custom caching logic for client-side fetches.

By effectively using memoization in your Next.js applications, you can optimize data fetching, enhance performance, and provide a more responsive user experience. Remember, a well-crafted caching strategy is essential for building performant and scalable Next.js applications.