Create a Browser-Based Spreadsheet: Libraries, Formulas, and Export

We have over 5 years of experience implementing spreadsheet components for dozens of clients, ensuring reliable and efficient solutions. Imagine developing a CRM where totals must be recalculated in real time for each row, and users copy data from Excel and paste it into a table. Spreadsheet is one of the most complex UI components: row virtualization, keyboard navigation, formulas, cell merging. Over five years, we've implemented dozens of such projects on React and Vue. In this article, we'll break down how to choose a ready-made library and integrate it with HyperFormula formulas to get a full Excel experience in the browser. Developing a spreadsheet from scratch can cost $10,000–$30,000, while integrating a ready-made solution starts from $1,000. The savings are clear. Our integration services start at $1,000, saving you up to $29,000 compared to custom development.

Advantages of Ready-Made Libraries Over Custom Development

A custom spreadsheet requires handling hundreds of edge cases: IME input, auto-filters, conditional formatting. Libraries like Handsontable and Fortune-Sheet have already been through that. For example, Handsontable contains over 300 API methods, and Fortune-Sheet has 200+ functions. Writing this from scratch takes 3–6 months of development. Integrating a ready-made solution takes 2–3 days. Moreover, popular libraries support virtualization: 10,000 rows render in 50 ms, which is 10 times faster than a naive implementation. According to Handsontable documentation, a commercial license starts at $149 per month, which pays back faster than developing your own solution.

Library Comparison: Which One Fits Your Project?

If you need complex formulas and Excel integration, the choice is Handsontable + HyperFormula. If your project is open source or has a limited budget, Fortune-Sheet gives you 80% of the functionality for free.

Integrating Formulas with HyperFormula

HyperFormula is an open-source formula engine (MIT) from the Handsontable team. It supports 386 functions, including VLOOKUP, SUMIF, DATE. Integration with Handsontable takes two days.

npm install hyperformula @handsontable/react @fortune-sheet/react xlsx

import { HyperFormula } from 'hyperformula'
import { HotTable } from '@handsontable/react'

function SpreadsheetWithFormulas() {
  const hfInstance = HyperFormula.buildEmpty({
    licenseKey: 'gpl-v3',
  })

  return (
    <HotTable
      formulas={{
        engine: hfInstance,
        sheetName: 'Sheet1',
      }}
      data={[
        ['Product', 'Quantity', 'Price', 'Total'],
        ['Product A', 10, 150, '=B2*C2'],
        ['Product B', 5, 300, '=B3*C3'],
        ['', '', 'Total:', '=SUM(D2:D3)'],
      ]}
    />
  )
}

Fortune-Sheet also supports formulas out of the box:

npm install @fortune-sheet/react

import { Workbook } from '@fortune-sheet/react'
import '@fortune-sheet/react/dist/index.css'

function FortuneSpreadsheet() {
  const [sheets, setSheets] = useState([
    {
      name: 'Sheet1',
      celldata: [
        { r: 0, c: 0, v: { v: 'Product', m: 'Product', ct: { fa: 'General', t: 'g' } } },
        { r: 0, c: 1, v: { v: 'Price', m: 'Price', ct: { fa: 'General', t: 'g' } } },
        { r: 1, c: 0, v: { v: 'Coffee', m: 'Coffee' } },
        { r: 1, c: 1, v: { v: 250, m: '250', ct: { fa: '#,##0.00', t: 'n' } } },
      ],
      row: 100,
      column: 26,
    },
  ])

  return (
    <div style={{ height: '600px' }}>
      <Workbook
        data={sheets}
        onChange={setSheets}
        showFormulaBar={true}
        showToolbar={true}
        lang="en"
      />
    </div>
  )
}

Exporting Data to Excel with SheetJS

We use the SheetJS library (xlsx). Export function for Handsontable:

import * as XLSX from 'xlsx'

function exportToExcel(hot: Handsontable) {
  const data = hot.getData()
  const headers = hot.getColHeader() as string[]
  const ws = XLSX.utils.aoa_to_sheet([headers, ...data])
  ws['!cols'] = headers.map(() => ({ wch: 20 }))
  const wb = XLSX.utils.book_new()
  XLSX.utils.book_append_sheet(wb, ws, 'Data')
  XLSX.writeFile(wb, `export-${new Date().toISOString().slice(0,10)}.xlsx`)
}

What's Included in the Implementation

1. Requirements analysis: formulas, data types, license restrictions (1 day).
2. Library selection and column configuration with validation (0.5 day).
3. Integration of HyperFormula or built-in formulas (2–3 days).
4. XLSX import/export via SheetJS (1 day).
5. API development for data persistence. Documentation and team training.

Our team guarantees a seamless integration with full support, and we have completed 30+ successful spreadsheet integrations.

When to Choose Virtual Scroll?

For tables with 10,000+ rows, definitely use virtualization. Handsontable and Fortune-Sheet support it out of the box, but you may need to configure viewport and renderAllRows: false. This speeds up rendering by 5–10 times.

Timeline: a basic editable table without formulas takes 2–3 days. A full spreadsheet with formulas and XLSX takes 5–7 days. Exact scope estimate is individual.

Cost and Solution Choice

A commercial Handsontable license costs from $149 per month—much better than investing 3–6 months in a custom component with the same capabilities. Fortune-Sheet (MIT) requires no license fees and is suitable for startups or internal tools with limited budgets. Integrating a ready-made library instead of building from scratch saves at least $1,500 upfront. For a corporate project needing formulas, 10,000+ rows, and Excel compatibility, Handsontable with HyperFormula delivers in 5–7 days. For a simple editable registry, Fortune-Sheet reduces the budget by 50–70%.

Get a consultation for your project — contact us. We'll help you choose the optimal solution and deploy it on time. Request a demo to see a working solution in action.

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.