Building Interactive Charts with Nivo for React

Note: When a React application needs to visualize tens of thousands of data points, choosing a chart library becomes critical. D3.js gives full control but requires hundreds of lines of code. Chart.js and Recharts are simpler but limited in customization. Nivo is the sweet spot: React component-based approach, support for SVG and Canvas, dozens of built-in chart types that can be customized for any task. Our engineers have used Nivo in production for over 5 years, delivering 50+ data visualization projects for fintech, e-commerce, and analytics. Development savings on visualization reach up to 30% compared to D3, and integration time is reduced by 2–3 times. Source: official Nivo documentation

A typical problem is incorrect data format. Nivo expects an array of objects with id and data fields. Hydration mismatch errors in SSR occur when data differs between client and server. Nivo renders correctly on the server as long as data is passed identically. We ensure stable operation at all stages.

Why Nivo is better than D3 for React applications

D3 works with the DOM at a low level, while Nivo provides ready-made React components. With D3, you must manage the lifecycle, updates, and destruction of charts yourself. Nivo handles this: when data changes, just pass new props, and the component re-renders with animation. D3 requires manual update and exit calls. Nivo also renders on the server (SSR) using React, while D3 typically works only on the client. This is critical for SEO and LCP. Additionally, Nivo makes it easy to switch between SVG and Canvas: for large datasets (10,000+ points), use Canvas—performance at 60 fps versus 30 fps for D3.

How to boost chart performance

When working with large datasets (over 5,000 points), we recommend:

• Use useCanvas instead of SVG.
• Memoize data with React.memo or useMemo.
• Limit points on screen via aggregation.
• Configure motionConfig to disable animations.

These techniques speed up rendering by 2–3 times and reduce CPU load.

Nivo vs D3 comparison

During development, we consider responsiveness: charts automatically adapt to container size via Nivo's Responsive components. This is especially important for dashboards viewed on different devices. We also configure tooltips to display correctly on mobile screens.

What is included

• Source code of chart components with custom tooltips.
• Documentation on data format and props.
• Integration with existing API.
• Mobile responsiveness.
• Team training (up to 1 hour).
• 3-month warranty.

Typical mistakes and how to avoid them

• Wrong data structure: ensure the array contains objects with id (string) and data (array of points).
• Missing keys when mapping: use React.memo and a unique key.
• Ignoring responsive: wrap in a container with a fixed height (min-height).
• Forgetting useMesh: without it, tooltips won't work.
• Missing dependencies: @nivo/core is required.

Process

1. Data analysis and visualization requirements.
2. Select chart types and prototype.
3. Configure backend to return data in the required format.
4. Integrate Nivo components, customize tooltips, legends.
5. Performance optimization (memoization, Canvas for large data).
6. Test on mobile devices and different screens.
7. Deploy and monitor.

Timeline

From 3 to 10 days depending on complexity. Pricing is individual.

npm install @nivo/line @nivo/bar @nivo/pie @nivo/heatmap @nivo/core

import { ResponsiveLine } from '@nivo/line';

function NivoLineChart({ data }) {
  // Nivo expects format: [{ id: 'series', data: [{ x, y }] }]
  const nivoData = [
    {
      id: 'Revenue',
      color: '#3b82f6',
      data: data.map(d => ({ x: d.date, y: d.revenue }))
    },
    {
      id: 'Target',
      color: '#f59e0b',
      data: data.map(d => ({ x: d.date, y: d.target }))
    }
  ];

  return (
    <div style={{ height: 350 }}>
      <ResponsiveLine
        data={nivoData}
        margin={{ top: 20, right: 120, bottom: 50, left: 70 }}
        xScale={{ type: 'time', format: '%Y-%m-%d', precision: 'day' }}
        xFormat="time:%d.%m.%Y"
        yScale={{ type: 'linear', stacked: false }}
        yFormat=" >-.0f"
        curve="monotoneX"
        axisLeft={{
          format: v => `${(v / 1000).toFixed(0)}k`,
          legend: 'Revenue (₽)',
          legendOffset: -60,
          legendPosition: 'middle'
        }}
        axisBottom={{
          format: '%d %b',
          tickValues: 'every 2 weeks'
        }}
        colors={{ scheme: 'paired' }}
        lineWidth={2}
        pointSize={4}
        enableArea
        areaOpacity={0.1}
        useMesh
        legends={[{
          anchor: 'bottom-right',
          direction: 'column',
          itemWidth: 100,
          itemHeight: 20
        }]}
        tooltip={({ point }) => (
          <div className="chart-tooltip">
            <strong>{point.data.xFormatted}</strong>
            <br />
            {point.serieId}: {Number(point.data.y).toLocaleString('ru')} ₽
          </div>
        )}
      />
    </div>
  );
}

import { ResponsiveBar } from '@nivo/bar';

function ConversionBarChart({ data }) {
  return (
    <div style={{ height: 300 }}>
      <ResponsiveBar
        data={data}
        keys={['conversion']}
        indexBy="page"
        margin={{ top: 10, right: 20, bottom: 60, left: 60 }}
        padding={0.4}
        valueScale={{ type: 'linear' }}
        colors={({ data }) => {
          if (data.conversion >= 5) return '#22c55e';
          if (data.conversion >= 2) return '#f59e0b';
          return '#ef4444';
        }}
        axisBottom={{ tickRotation: -45 }}
        axisLeft={{ format: v => `${v}%` }}
        label={d => `${d.value}%`}
        tooltip={({ data, value }) => (
          <div className="chart-tooltip">
            <strong>{data.page}</strong>: {value}% conversion
          </div>
        )}
      />
    </div>
  );
}

import { ResponsiveCalendar } from '@nivo/calendar';

function ActivityCalendar({ data }) {
  // data: [{ day: '2024-03-28', value: 42 }]
  return (
    <div style={{ height: 200 }}>
      <ResponsiveCalendar
        data={data}
        from="2024-01-01"
        to="2024-12-31"
        emptyColor="#f3f4f6"
        colors={['#dbeafe', '#93c5fd', '#3b82f6', '#1d4ed8']}
        margin={{ top: 20, right: 20, bottom: 20, left: 20 }}
        yearSpacing={40}
        monthBorderColor="#ffffff"
        dayBorderWidth={2}
        dayBorderColor="#ffffff"
        tooltip={({ day, value }) => (
          <div className="chart-tooltip">{day}: {value} events</div>
        )}
      />
    </div>
  );
}

Order turnkey development — get a consultation and prototype in 2 days. Contact us to discuss your project. Our engineers with 5+ years of experience will help you implement data visualization of any complexity.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.