Comprehensive Guide: Using Recharts in Next.js with TypeScript

I am facing an issue with adding Recharts in a Next.js server component because Recharts runs only on the client side. If you are using Shadcn, you should check the Shadcn chart component, which uses Recharts underneath. In this tutorial, we will learn how to add Recharts in a Next.js client component.

Recharts runs only on the client side because it relies on the browser’s DOM to render charts. Next.js distinguishes between server components and client components, and any component that requires client-side rendering should be marked as a client component.

Table of Contents on Nextjs Recharts

Root Causes of Issues

When integrating Recharts into a Next.js application with TypeScript, developers often encounter several issues:

Server-Side Rendering (SSR) Conflicts: Recharts is primarily a client-side library and can cause errors during server-side rendering in Next.js.
TypeScript Type Incompatibilities: The types provided by Recharts may not always align perfectly with Next.js’s expectations, especially when using dynamic imports.
Performance Issues: Improper use of Recharts can lead to performance bottlenecks, especially in larger applications.
Styling Conflicts: Recharts’ default styles may conflict with global styles or CSS-in-JS solutions used in Next.js projects.

Best Practices for Adding Recharts in Server or Client Components

1. For Server Components:

Avoid Direct Usage: Server components should not directly render Recharts components.
Data Preparation: Use server components to fetch and prepare data for charts, then pass this data to client components.

2. For Client Components:

Use the “use client” Directive: Always add "use client" at the top of files containing Recharts components.
Dynamic Imports: Utilize Next.js’s dynamic import feature to load Recharts components.

"use client";
//Example syntax
import dynamic from 'next/dynamic';

const DynamicLineChart = dynamic(() => import('recharts').then(mod => mod.LineChart), { ssr: false });

export default function ChartComponent({ data }) {
  return (
    <DynamicLineChart data={data}>
      {/* Chart configuration */}
    </DynamicLineChart>
  );
}

In our case we have ChartComponent.tsx

"use client";

import React from "react";
import {
  LineChart,
  Line,
  XAxis,
  YAxis,
  CartesianGrid,
  Tooltip,
  Legend,
  ResponsiveContainer,
} from "recharts";

interface DataPoint {
  name: string;
  visits: number;
  orders: number;
}

interface ChartComponentProps {
  data: DataPoint[];
}

const ChartComponent: React.FC<ChartComponentProps> = ({ data }) => {
  return (
    <ResponsiveContainer width="100%" height={300}>
      <LineChart data={data}>
        <CartesianGrid strokeDasharray="3 3" />
        <XAxis dataKey="name" />
        <YAxis />
        <Tooltip />
        <Legend />
        <Line type="monotone" dataKey="visits" stroke="#8884d8" />
        <Line type="monotone" dataKey="orders" stroke="#82ca9d" />
      </LineChart>
    </ResponsiveContainer>
  );
};

export default ChartComponent;

3. Proper Use of Recharts

Responsive Containers: Always wrap your charts in a ResponsiveContainer for better responsiveness.
Memoization: Use React.memo or useMemo for chart components to prevent unnecessary re-renders.
Custom Components: Create custom wrapper components for frequently used chart types.

Example of a custom wrapper:

"use client";

import React from 'react';
import { ResponsiveContainer, LineChart, Line, XAxis, YAxis, Tooltip, Legend } from 'recharts';

interface DataPoint {
  name: string;
  value: number;
}

interface CustomLineChartProps {
  data: DataPoint[];
  xDataKey: string;
  yDataKey: string;
}

const CustomLineChart: React.FC<CustomLineChartProps> = React.memo(({ data, xDataKey, yDataKey }) => (
  <ResponsiveContainer width="100%" height={300}>
    <LineChart data={data}>
      <XAxis dataKey={xDataKey} />
      <YAxis />
      <Tooltip />
      <Legend />
      <Line type="monotone" dataKey={yDataKey} stroke="#8884d8" />
    </LineChart>
  </ResponsiveContainer>
));

export default CustomLineChart;

4. Optimizing Recharts in Next.js

Lazy Loading: Use dynamic imports to lazy load chart components.
Code Splitting: Separate chart components into their own files for better code splitting.
Caching: Implement caching strategies for chart data, especially if it’s fetched from an API.
Throttling and Debouncing: Apply these techniques for charts that update frequently based on user interactions.

Example of lazy loading with suspense in server component

import dynamic from 'next/dynamic';
import { Suspense } from 'react';

const DynamicChart = dynamic(() => import('./ChartComponent'), {
  loading: () => <p>Loading chart...</p>,
  ssr: false
});

export default function Dashboard() {
  return (
    <Suspense fallback={<div>Loading...</div>}>
      <DynamicChart />
    </Suspense>
  );
}

5. TypeScript Considerations

Proper Typing: Define clear interfaces for your chart data and props.
Type Assertions: Use type assertions judiciously when working with dynamic imports.
Generic Components: Create generic chart components for increased reusability.

Example of a generic chart component:

import React from 'react';
import { ResponsiveContainer, LineChart, Line, XAxis, YAxis, Tooltip, Legend } from 'recharts';

interface DataPoint {
  [key: string]: string | number;
}

interface GenericChartProps<T extends DataPoint> {
  data: T[];
  xDataKey: keyof T;
  yDataKey: keyof T;
}

function GenericChart<T extends DataPoint>({ data, xDataKey, yDataKey }: GenericChartProps<T>) {
  return (
    <ResponsiveContainer width="100%" height={300}>
      <LineChart data={data}>
        <XAxis dataKey={xDataKey as string} />
        <YAxis />
        <Tooltip />
        <Legend />
        <Line type="monotone" dataKey={yDataKey as string} stroke="#8884d8" />
      </LineChart>
    </ResponsiveContainer>
  );
}

export default GenericChart;

6. Common Pitfalls to Avoid

Rendering Charts Server-Side: Always ensure Recharts components are rendered client-side only. Overcomplicating Charts: Start with simple charts and add complexity as needed. Neglecting Mobile Optimization: Always test and optimize charts for mobile devices. Ignoring Accessibility: Ensure your charts are accessible, including proper aria labels and color contrasts.

Conclusion:
By following these guidelines and best practices, you can effectively integrate Recharts into your Next.js application with TypeScript, avoiding common pitfalls and ensuring optimal performance and maintainability.