From 9f602941740cbe5204be9206237622385aad69e6 Mon Sep 17 00:00:00 2001 From: Afzal Ahmad Date: Tue, 17 Nov 2026 15:51:03 +0100 Subject: [PATCH 1/2] docs: worker option lands in 1.x; the main-thread writer yields (javascript-excel 2.0.0-alpha.7); measure the bundle size (#110) - Depend on javascript-excel ^2.0.0-alpha.7, whose writer returns to the event loop about every 16 ms (library and playground). - docs/api.md, README, the package README and docs/triage-1.0.md: the worker option comes in a 1.x release, not 1.0; until then a large export on the main thread keeps the page responsive. - fixtures/bundle-size + scripts/bundlers.mjs: what react-data-export adds to a Vite + React 19 production build per usage, against React alone and 0.6.0, printed in the Bundlers job summary. The numbers replace the #110 placeholder in docs/triage-1.0.md. --- .changeset/javascript-excel-alpha-7.md | 5 +++ README.md | 1 + apps/playground/package.json | 2 +- docs/api.md | 18 ++++---- docs/triage-1.0.md | 8 ++-- fixtures/README.md | 1 + fixtures/bundle-size/package.json | 8 ++++ fixtures/bundle-size/src/all.jsx | 25 +++++++++++ fixtures/bundle-size/src/baseline.jsx | 4 ++ fixtures/bundle-size/src/dataset.jsx | 7 ++++ fixtures/bundle-size/src/table.jsx | 16 +++++++ fixtures/bundle-size/src/v0.6.jsx | 14 +++++++ fixtures/bundle-size/vite.config.js | 13 ++++++ package-lock.json | 10 ++--- packages/react-data-export/README.md | 2 +- packages/react-data-export/package.json | 2 +- scripts/bundlers.mjs | 55 ++++++++++++++++++++++++- 17 files changed, 170 insertions(+), 21 deletions(-) create mode 100644 .changeset/javascript-excel-alpha-7.md create mode 100644 fixtures/bundle-size/package.json create mode 100644 fixtures/bundle-size/src/all.jsx create mode 100644 fixtures/bundle-size/src/baseline.jsx create mode 100644 fixtures/bundle-size/src/dataset.jsx create mode 100644 fixtures/bundle-size/src/table.jsx create mode 100644 fixtures/bundle-size/src/v0.6.jsx create mode 100644 fixtures/bundle-size/vite.config.js diff --git a/.changeset/javascript-excel-alpha-7.md b/.changeset/javascript-excel-alpha-7.md new file mode 100644 index 0000000..53bf05e --- /dev/null +++ b/.changeset/javascript-excel-alpha-7.md @@ -0,0 +1,5 @@ +--- +"react-data-export": patch +--- + +Depend on javascript-excel `^2.0.0-alpha.7`. Its writer returns to the event loop about every 16 ms, so a large `.xlsx` export on the main thread no longer freezes the page, and `signal`/`abort()` take effect while it runs. diff --git a/README.md b/README.md index f620637..87bcc3f 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,7 @@ Export data from React to `.xlsx` and `.csv`. - **1.0 has a new API.** It is rebuilt on [javascript-excel](https://github.com/securedeveloper/javascript-excel) 2.0, and its main entry has no `` / `` / ``. The 0.6 API ships only as the deprecated `react-data-export/legacy` entry: supported for all of 1.x, removed in 2.0. See [Migrating from 0.x](#migrating-from-0x). - **1.0 prereleases are on npm's `next` tag:** `npm install react-data-export@next`. They have dataset export (`exportDataset`, `exportWorkbook`, `useExcelExport`, ``) and table export for an HTML `` (`exportTable`, `useTableExport`, ``), as specified in [docs/api.md](docs/api.md), built on javascript-excel 2.0's `fromDataset`, `fromTable`, writer and download. As an alpha, the API may still change before 1.0.0. Coming from 0.x: the [migration guide](docs/migration.md). +- **Big exports stay responsive.** Exports run on the main thread. On javascript-excel 2.0.0-alpha.7 and later (the version react-data-export requires), the `.xlsx` writer returns to the event loop about every 16 ms, so the page keeps rendering and handling input during a large export, and `abort()` works while it runs. A `worker` option, which writes the file in a Web Worker on top of `javascript-excel/worker`, comes in a 1.x release after 1.0.0, not in 1.0 ([docs/api.md §7](docs/api.md#7-errors-abort-and-progress)). ```tsx import { ExcelExport } from 'react-data-export'; diff --git a/apps/playground/package.json b/apps/playground/package.json index 268992a..18107eb 100644 --- a/apps/playground/package.json +++ b/apps/playground/package.json @@ -10,7 +10,7 @@ "test": "vitest run" }, "dependencies": { - "javascript-excel": "^2.0.0-alpha.3", + "javascript-excel": "^2.0.0-alpha.7", "react": "^19.3.1", "react-data-export": "1.0.0-alpha.3", "react-dom": "^19.3.1" diff --git a/docs/api.md b/docs/api.md index 5e7621a..d026279 100644 --- a/docs/api.md +++ b/docs/api.md @@ -1,6 +1,6 @@ # react-data-export 1.0: API design (dataset module) -Status: **design decided (2026-11-16); the dataset module is implemented** (RDE-1.9) on **javascript-excel ≥ 2.0.0-alpha.2** (see [§9](#9-dependencies-and-order)). It is not published yet. Table export (module B, [§13](#13-table-export)) is designed and implemented in RDE-1.17. +Status: **design decided (2026-11-16); the dataset module is implemented** (RDE-1.9) on **javascript-excel ≥ 2.0.0-alpha.7** (see [§9](#9-dependencies-and-order)), and ships in the 1.0 prereleases on npm's `next` tag. Table export (module B, [§13](#13-table-export)) is designed and implemented in RDE-1.17. This document covers module A, **dataset export** (`exportDataset`, `exportWorkbook`, `useExcelExport`, ``), and module B, **table export** (`exportTable`, `useTableExport`, ``, [§13](#13-table-export)). @@ -263,10 +263,11 @@ export function ExcelExport(props: ExcelExportProps): ReactElement; - react-data-export's own misuse errors (CSV with several sheets, `dataset` and `workbook` both or neither, an unknown `format`) are `TypeError`s. That's how javascript-excel treats invalid options too. - **Abort.** `signal` reaches `toBlob`, which checks it between sheet chunks. It is also checked before building and before the download starts. Every export starts by yielding once (one microtask) and re-checking the signal before it builds anything. `toCsvBlob` is synchronous, so without that yield a CSV export started in an effect would finish, download included, before React 18/19 StrictMode's simulated unmount could abort it, and the documented auto-export recipe would save the file twice in development. An abort rejects with `signal.reason` (a `DOMException` `AbortError` by default). `toCsvBlob` is synchronous, so a CSV export can only be aborted before it starts. - **Progress.** `onProgress` receives javascript-excel's `Progress` (`phase`, `sheet`, `ratio` from 0 to 1, non-decreasing) from `toBlob`. The building phase (`fromDataset`) is synchronous and reports nothing, so the first progress event comes from the writer. CSV reports no progress. -- **Big data.** Large exports run on the main thread in 1.0. Off-main-thread writing comes with javascript-excel's worker entry (its JSE-8): - - `fromDataset` has to run on the main thread, because accessors are functions and can't be sent to a worker. +- **Big data: the main thread stays responsive.** In 1.0, exports run on the main thread. From javascript-excel 2.0.0-alpha.7 (the lowest version react-data-export depends on, §9), `toBlob` returns to the event loop about every 16 ms while it writes. So a large `.xlsx` export doesn't freeze the page: frames render, input is handled, and `abort()` or an aborted `signal` takes effect while the file is being written. The output bytes are the same as without the pauses. Building the sheet (`fromDataset`, `fromTable`) and writing CSV (`toCsvBlob`) are still synchronous. +- **Worker: 1.x, not 1.0** (decided 2026-11-17). javascript-excel's worker entry, `javascript-excel/worker` (its §5.5), has existed since 2.0.0-alpha.1. react-data-export adds it after 1.0.0, in a 1.x minor release: + - `fromDataset` and `fromTable` have to run on the main thread: accessors are functions and can't be sent to a worker, and the table is in the page. - The resulting sheet is plain data, and can be written in a worker. - - When JSE-8 ships, `ExportOptions` gains `worker?: WorkerClient`. That is additive, not a breaking change. Until then this is listed under 1.x, not 1.0. + - `ExportOptions` gains `worker?: WorkerClient`. That's additive, not a breaking change, so it doesn't have to wait for 2.0. ## 8. SSR and `"use client"` @@ -287,9 +288,10 @@ export function ExcelExport(props: ExcelExportProps): ReactElement; | `toCsvBlob`, `CsvWriteOptions` | `javascript-excel/csv`, §5.3 | 2.0.0-alpha.1 | | `download` | `javascript-excel/dom`, §5.4 | 2.0.0-alpha.1 (JSE-7) | | `fromTable`, `FromTableOptions`, `TableElement` (§13) | `javascript-excel/dom`, §5.4 | 2.0.0-alpha.1 (JSE-7) | -| `WorkerClient` (1.x only) | `javascript-excel/worker`, §5.5 | planned (JSE-8) | +| `toBlob` returning to the event loop while it writes (§7) | core entry, §5.1 | 2.0.0-alpha.7 | +| `WorkerClient` (1.x only, §7) | `javascript-excel/worker`, §5.5 | 2.0.0-alpha.1 (JSE-8) | -So react-data-export depends on `"javascript-excel": "^2.0.0-alpha.2"` ([Q6](#12-design-decisions)), the first prerelease with `fromDataset`/`fromDatasets`. Nothing in react-data-export reimplements them. +So react-data-export depends on `"javascript-excel": "^2.0.0-alpha.7"` ([Q6](#12-design-decisions)). 2.0.0-alpha.2 was the first prerelease with `fromDataset`/`fromDatasets`, and 2.0.0-alpha.7 is the first whose writer yields to the browser. Nothing in react-data-export reimplements them. ## 10. Feature coverage @@ -306,7 +308,7 @@ The 1.0 feature list, and where each one comes from: | Totals row / formulas, hyperlinks (#103 #99 #175) | `total` on columns; cells with `formula` / `hyperlink` | | RTL sheets (#109 #162 #157) | `rightToLeft` (`DatasetOptions`) | | CSV options: delimiter, BOM, injection guard (#138) | `format: 'csv'` + `csv` (`CsvWriteOptions`); the injection guard is on by default | -| Big data: progress, `AbortSignal` (#154 #170 #153) | `onProgress`, `signal`, hook `abort()`; worker in 1.x (§7) | +| Big data: progress, `AbortSignal` (#154 #170 #153) | `onProgress`, `signal`, hook `abort()`; the writer yields to the browser on the main thread; worker in 1.x (§7) | | SSR-safe, no `window` at import (#168 family) | §8 | | Export an HTML table (#172) | `exportTable`, `useTableExport`, `` over `fromTable` (§13) | @@ -339,7 +341,7 @@ These were the open questions of the review. Each one is decided, and the sectio **Q5. `` triggers.** Decided (2026-11-16): a default button or a render prop, with no `cloneElement` (§6). The 0.x-style `element` with an injected `onClick` is not carried over, because it breaks with components that don't forward `onClick` and with fragments. -**Q6. javascript-excel range during the 2.0 prereleases.** Decided (2026-11-16): `"javascript-excel": "^2.0.0-alpha.2"` (§9). A caret on a prerelease matches only later 2.0.0 prereleases and 2.0.0 itself. An exact pin bumped with each alpha was not taken. +**Q6. javascript-excel range during the 2.0 prereleases.** Decided (2026-11-16): a caret range on a prerelease, `"javascript-excel": "^2.0.0-alpha.2"` at the time and `^2.0.0-alpha.7` now (§9). A caret on a prerelease matches only later 2.0.0 prereleases and 2.0.0 itself. An exact pin bumped with each alpha was not taken. **Q7. Accessor fields.** Decided (2026-11-16): javascript-excel's `key` / `path` / `value` / `index` pass through unchanged (§3). That gives one documented shape for every framework and no ambiguity about `'a.b'`. A combined react-data-export field mapped to `key` or `path`, which javascript-excel's Q18 would allow, was not taken. diff --git a/docs/triage-1.0.md b/docs/triage-1.0.md index e923ed6..1786495 100644 --- a/docs/triage-1.0.md +++ b/docs/triage-1.0.md @@ -96,7 +96,7 @@ Thanks to the community pull requests whose ideas shaped 1.0: | #85 | Error by importing the project | Fixed in 1.0.0-alpha.1 | No `tempa-xlsx`, `xlsx`, `file-saver` or `prop-types` any more; the only dependency is javascript-excel (no runtime deps). Import errors from the old dependency chain can't happen. | | #90 | issue in react js dependence added time Module not found: Can't resolve 'react-data-export' using | Fixed in 1.0.0-alpha.1 | Same: the 0.x dependency chain is gone; `exports` map with ESM + CJS + types, smoke-tested from the packed tarball in CI. | | #100 | Module not found: Can't resolve 'prop-types' in \node_modules\react-data-export\dist\ExcelPlugin\components | Fixed in 1.0.0-alpha.1 | `prop-types` is not used in 1.0. | -| #110 | xlsx dependency blows up webpack bundle size | Fixed in 1.0.0-alpha.1 | `xlsx`/`tempa-xlsx` are no longer dependencies; javascript-excel has zero runtime dependencies and per-entry tree-shaking (writer, CSV, DOM are separate entries). Bundle size: [placeholder, measure in the bundler matrix]. | +| #110 | xlsx dependency blows up webpack bundle size | Fixed in 1.0.0-alpha.1 | `xlsx`/`tempa-xlsx` are no longer dependencies; javascript-excel has zero runtime dependencies and per-entry tree-shaking (writer, CSV, DOM are separate entries). Bundle size, measured with the bundler matrix's `bundle-size` fixture (`npm run bundlers -- bundle-size`: Vite 8.3.8 + React 19.3.1 production builds, react-data-export 1.0.0-alpha.3 on javascript-excel 2.0.0-alpha.7, minus the same app with React alone). `exportDataset` adds 72.8 KiB minified (24.7 KiB gzip), `` 78.4 KiB (27.7 KiB gzip), every export of the main entry 90.0 KiB (31.5 KiB gzip). 0.6.0's `` adds 741.1 KiB (266.3 KiB gzip). | | #168 | Module not found can't resolve 'fs' in node_modules\tempa-xlsx | Fixed in 1.0.0-alpha.1 | No `tempa-xlsx`, so no `fs` import; covered by the CRA/webpack 5 fixture in the bundler matrix (RDE-1.11). | | #169 | Why does xlsx get installed into my package.json when installing this package | Fixed in 1.0.0-alpha.1 | `xlsx` is not a dependency or a required peer in 1.0. | | #173 | Application crash when using vitejs | Fixed in 1.0.0-alpha.1 | No `cptable`/`xlsx` code; Vite fixture in the bundler matrix. | @@ -218,7 +218,7 @@ Thanks to the community pull requests whose ideas shaped 1.0: | # | title | disposition | how / reason | |---|---|---|---| | #154 | The maximum you can export to excel is 1299 rows, how to increase the number of exported rows? | Fixed in 1.0.0-alpha.1 | Measured on alpha.1 (Node 24): 1,300 / 10,000 / 100,000 rows × 3 columns export and read back complete (100k rows: 318 ms, 2.1 MB). | -| #170 | Browser window stops responding | Still open, tracked | The javascript-excel writer works in chunks and yields; a worker option (`javascript-excel/worker`) is planned for react-data-export 1.x. Keep open until the worker option ships. | +| #170 | Browser window stops responding | Still open, tracked | From javascript-excel 2.0.0-alpha.7, which react-data-export requires, the writer returns to the event loop about every 16 ms, so a large export on the main thread no longer freezes the page. The `worker` option (`javascript-excel/worker`) lands in react-data-export 1.x, not 1.0 (decided 2026-11-17). Keep open until the worker option ships. | ### Out of scope for 1.0 @@ -653,6 +653,6 @@ Each comment is followed by the footer above. "Close" means close after posting; - **Side-by-side blocks (#134):** `fromDatasets` places a block next to the previous one only with a negative `offset.rows`. A clearer option (for example `offset: { beside: true }`) is a javascript-excel ticket. - **Excel checks (#76, #94):** open a 1.0.0-alpha.1 single-sheet and multi-sheet file in Excel for Mac and Windows; close both issues with the result. -- **Bundle size (#110):** the bundler matrix (RDE-1.11) can record the size of a minimal app with and without react-data-export, so the comment can quote a measured number instead of `[placeholder]`. -- **Worker option (#170):** `ExportOptions.worker` on javascript-excel's `WorkerClient` (docs/api.md §7), for react-data-export 1.x. +- **Bundle size (#110):** measured (2026-11-17) with the bundler matrix's `bundle-size` fixture; the numbers are in the #110 row in §2. The `Bundlers` CI job prints the same table in its summary on every run. +- **Worker option (#170):** `ExportOptions.worker` on javascript-excel's `WorkerClient` (docs/api.md §7), in react-data-export 1.x, not 1.0 (decided 2026-11-17). Until then, the main-thread writer yields to the browser (javascript-excel 2.0.0-alpha.7). diff --git a/fixtures/README.md b/fixtures/README.md index 478fcb1..1208e6d 100644 --- a/fixtures/README.md +++ b/fixtures/README.md @@ -7,6 +7,7 @@ Small apps that install the **packed** react-data-export tarball, exactly as use | `vite-react19` | Vite 8 | 19 | production build of ``, `useExcelExport`, `exportDataset` and `useTableExport(ref)` behind a custom button; the bundle has no `fs`/`tempa-xlsx`/`jszip`/`cptable` | | `next-app` | Next.js 16 (App Router, webpack and Turbopack builds) | 19 | `next build`: a server component renders `` (a client component through `"use client"`) and client components use the hook and `` on a table with a `colspan` header; the page is prerendered on the server (the check looks for the table and the button in the HTML), so importing the package on the server must not crash | | `webpack5-cra` | Create React App 5 (`react-scripts`, webpack 5) | 18 | production build with CRA's default config, which has no Node polyfills, including `` (the `javascript-excel/dom` subpath through webpack 5's exports-map resolution) | +| `bundle-size` | Vite 8 | 19 | not a compatibility check: one production build per usage (`exportDataset` alone, `` alone, every export, and 0.6.0's `` for comparison) and React alone, and a table of what each adds (minified, gzip -9, brotli -11), in the log and the job summary (#110) | | `react17-ts` | Vite 8 | 17, with `@types/react` 17 | `tsc` against the published types, including `exportTable(ref, { format: "csv" })` with React 17's `useRef(null)`, then a production build | These replace the failures reported in #168 (`Can't resolve 'fs'` with react-scripts 5), #173 (`cptable is not defined` with Vite), #177 (`Could not resolve "xlsx"` with Vite) and #182 (`jszip is not a constructor`). All of them came from the 0.x dependency on `tempa-xlsx`, `jszip` and `file-saver`, which 1.0 no longer has. diff --git a/fixtures/bundle-size/package.json b/fixtures/bundle-size/package.json new file mode 100644 index 0000000..45b863b --- /dev/null +++ b/fixtures/bundle-size/package.json @@ -0,0 +1,8 @@ +{ + "name": "fixture-bundle-size", + "private": true, + "type": "module", + "scripts": { "build": "vite build" }, + "dependencies": { "react": "19.3.1", "react-dom": "19.3.1", "react-data-export-0.6": "npm:react-data-export@0.6.0", "prop-types": "15.8.1" }, + "devDependencies": { "vite": "8.3.8" } +} diff --git a/fixtures/bundle-size/src/all.jsx b/fixtures/bundle-size/src/all.jsx new file mode 100644 index 0000000..4e4804c --- /dev/null +++ b/fixtures/bundle-size/src/all.jsx @@ -0,0 +1,25 @@ +// Every export of the main entry, used: the upper bound for react-data-export. +import { useRef } from "react"; +import { createRoot } from "react-dom/client"; +import { ExcelExport, ExportTableButton, exportDataset, exportTable, exportWorkbook, isExcelError, sanitizeSheetName, useExcelExport, useTableExport } from "react-data-export"; + +const people = { columns: [{ title: "Name", key: "name" }], data: [{ name: "Ada" }] }; + +function App() { + const ref = useRef(null); + const hook = useExcelExport(); + const table = useTableExport(ref); + return ( + <> +
Ada
+ Component + Table button + + + + + + ); +} + +createRoot(document.getElementById("root")).render(); diff --git a/fixtures/bundle-size/src/baseline.jsx b/fixtures/bundle-size/src/baseline.jsx new file mode 100644 index 0000000..ee1e89d --- /dev/null +++ b/fixtures/bundle-size/src/baseline.jsx @@ -0,0 +1,4 @@ +// React alone: the app every other entry is measured against. +import { createRoot } from "react-dom/client"; + +createRoot(document.getElementById("root")).render(); diff --git a/fixtures/bundle-size/src/dataset.jsx b/fixtures/bundle-size/src/dataset.jsx new file mode 100644 index 0000000..099247c --- /dev/null +++ b/fixtures/bundle-size/src/dataset.jsx @@ -0,0 +1,7 @@ +// The smallest dataset export: one exportDataset call behind a button. +import { createRoot } from "react-dom/client"; +import { exportDataset } from "react-data-export"; + +const people = { columns: [{ title: "Name", key: "name" }], data: [{ name: "Ada" }] }; + +createRoot(document.getElementById("root")).render(); diff --git a/fixtures/bundle-size/src/table.jsx b/fixtures/bundle-size/src/table.jsx new file mode 100644 index 0000000..bec8745 --- /dev/null +++ b/fixtures/bundle-size/src/table.jsx @@ -0,0 +1,16 @@ +// Table export: on a table ref. +import { useRef } from "react"; +import { createRoot } from "react-dom/client"; +import { ExportTableButton } from "react-data-export"; + +function App() { + const ref = useRef(null); + return ( + <> +
Ada
+ Export + + ); +} + +createRoot(document.getElementById("root")).render(); diff --git a/fixtures/bundle-size/src/v0.6.jsx b/fixtures/bundle-size/src/v0.6.jsx new file mode 100644 index 0000000..45316a3 --- /dev/null +++ b/fixtures/bundle-size/src/v0.6.jsx @@ -0,0 +1,14 @@ +// react-data-export 0.6.0 (the current `latest` on npm), the same one-sheet export. +import { createRoot } from "react-dom/client"; +import ReactExport from "react-data-export-0.6"; + +const { ExcelFile } = ReactExport; +const { ExcelSheet, ExcelColumn } = ExcelFile; + +createRoot(document.getElementById("root")).render( + Export}> + + + + , +); diff --git a/fixtures/bundle-size/vite.config.js b/fixtures/bundle-size/vite.config.js new file mode 100644 index 0000000..812bbb9 --- /dev/null +++ b/fixtures/bundle-size/vite.config.js @@ -0,0 +1,13 @@ +// One production build per entry (ENTRY=baseline|dataset|table|all|v0.6), so +// each output is exactly what that app ships. scripts/bundlers.mjs compares +// them with the baseline (React alone). +const entry = process.env.ENTRY ?? "baseline"; + +export default { + logLevel: "warn", + build: { + outDir: `dist/${entry}`, + emptyOutDir: true, + rollupOptions: { input: `src/${entry}.jsx` }, + }, +}; diff --git a/package-lock.json b/package-lock.json index bc6ceab..f6eb414 100644 --- a/package-lock.json +++ b/package-lock.json @@ -21,7 +21,7 @@ }, "apps/playground": { "dependencies": { - "javascript-excel": "^2.0.0-alpha.3", + "javascript-excel": "^2.0.0-alpha.7", "react": "^19.3.1", "react-data-export": "1.0.0-alpha.3", "react-dom": "^19.3.1" @@ -2188,9 +2188,9 @@ "license": "MIT" }, "node_modules/javascript-excel": { - "version": "2.0.0-alpha.3", - "resolved": "https://registry.npmjs.org/javascript-excel/-/javascript-excel-2.0.0-alpha.3.tgz", - "integrity": "sha512-KMXUPFmqWwWYKy9V4Mvk7A4s5RJXHimpjqzTgGBs3bDHVFiwhoAEBMWSN84OclTOoroUGZYLvh5aux8ictK6Dg==", + "version": "2.0.0-alpha.7", + "resolved": "https://registry.npmjs.org/javascript-excel/-/javascript-excel-2.0.0-alpha.7.tgz", + "integrity": "sha512-Vgehcr5hl/jqxhuE2Mh0F7VeKrl0DdjdYgmT2RIAFfxY9ecYm3ZCY15ohOpU/gKaWzZgH7ELxgtwR8OxS3CjCA==", "license": "MIT", "engines": { "node": ">=22" @@ -4156,7 +4156,7 @@ "version": "1.0.0-alpha.3", "license": "MIT", "dependencies": { - "javascript-excel": "^2.0.0-alpha.3" + "javascript-excel": "^2.0.0-alpha.7" }, "devDependencies": { "@arethetypeswrong/cli": "^0.18.5", diff --git a/packages/react-data-export/README.md b/packages/react-data-export/README.md index 8dd22d2..8df8336 100644 --- a/packages/react-data-export/README.md +++ b/packages/react-data-export/README.md @@ -25,7 +25,7 @@ function Orders() { } ``` -There are also plain async functions (`exportDataset`, `exportWorkbook`, `exportTable`) and hooks (`useExcelExport`, `useTableExport`). Every export resolves with `{ blob, filename, format, warnings }`. The full API is in [docs/api.md](https://github.com/securedeveloper/react-data-export/blob/main/docs/api.md). +There are also plain async functions (`exportDataset`, `exportWorkbook`, `exportTable`) and hooks (`useExcelExport`, `useTableExport`). Every export resolves with `{ blob, filename, format, warnings }`. A large `.xlsx` export doesn't freeze the page: the writer returns to the event loop about every 16 ms. A Web Worker option is planned for a 1.x release. The full API is in [docs/api.md](https://github.com/securedeveloper/react-data-export/blob/main/docs/api.md). Moving from 0.x in steps? `react-data-export/legacy` keeps ``, `` and `` working on 1.0 (deprecated, removed in 2.0); see the [quick path](https://github.com/securedeveloper/react-data-export/blob/main/docs/migration.md#11-quick-path-react-data-exportlegacy). diff --git a/packages/react-data-export/package.json b/packages/react-data-export/package.json index b6722d5..0b1bf39 100644 --- a/packages/react-data-export/package.json +++ b/packages/react-data-export/package.json @@ -80,6 +80,6 @@ "vitest": "^5.1.0" }, "dependencies": { - "javascript-excel": "^2.0.0-alpha.3" + "javascript-excel": "^2.0.0-alpha.7" } } diff --git a/scripts/bundlers.mjs b/scripts/bundlers.mjs index 9f207bd..1f9ad9b 100644 --- a/scripts/bundlers.mjs +++ b/scripts/bundlers.mjs @@ -11,6 +11,7 @@ import { execFileSync } from 'node:child_process'; import { appendFileSync, cpSync, existsSync, mkdtempSync, readFileSync, readdirSync, rmSync, statSync, writeFileSync } from 'node:fs'; import { tmpdir } from 'node:os'; import { join, resolve } from 'node:path'; +import { brotliCompressSync, constants, gzipSync } from 'node:zlib'; const root = resolve(import.meta.dirname, '..'); const pkgDir = join(root, 'packages/react-data-export'); @@ -55,7 +56,55 @@ function scanClientBundle(dir) { return `${js.length} JS files, ${(bytes / 1024).toFixed(0)} KiB`; } +const kib = (n) => `${(n / 1024).toFixed(1)} KiB`; + +/** Size of the JavaScript an app ships: minified, gzip -9 and brotli -11, summed over its files. */ +function jsSize(dir) { + const size = { min: 0, gzip: 0, brotli: 0 }; + for (const file of filesIn(dir, /\.js$/)) { + const buf = readFileSync(file); + size.min += buf.length; + size.gzip += gzipSync(buf, { level: 9 }).length; + size.brotli += brotliCompressSync(buf, { params: { [constants.BROTLI_PARAM_QUALITY]: 11 } }).length; + } + return size; +} + +// fixtures/bundle-size: what react-data-export adds to a Vite + React 19 +// production build, per usage, against the same app without it (#110). +const SIZE_ENTRIES = [ + ['dataset', '1.0: `exportDataset` behind a button'], + ['table', '1.0: `` on a table'], + ['all', '1.0: every export of the main entry'], + ['v0.6', '0.6.0: `` + `` + ``'], +]; +const sizeTables = []; + const CHECKS = { + 'bundle-size': (app) => { + const build = (entry) => { + run('npm', ['run', 'build'], app, { ENTRY: entry }); + return jsSize(join(app, 'dist', entry)); + }; + const version = (name) => JSON.parse(readFileSync(join(app, 'node_modules', name, 'package.json'), 'utf8')).version; + const base = build('baseline'); + const rows = SIZE_ENTRIES.map(([entry, what]) => { + const s = build(entry); + // 1.0 builds get the same no-fs/tempa-xlsx/jszip scan as the other fixtures; 0.6.0 has them all. + if (entry !== 'v0.6') scanClientBundle(join(app, 'dist', entry)); + return `| ${what} | +${kib(s.min - base.min)} | +${kib(s.gzip - base.gzip)} | +${kib(s.brotli - base.brotli)} |`; + }); + sizeTables.push( + [ + `Added to a Vite ${version('vite')} + React ${version('react')} production build by react-data-export ${version('react-data-export')} on javascript-excel ${version('javascript-excel')} (baseline, React alone: ${kib(base.min)} minified, ${kib(base.gzip)} gzip):`, + '', + '| app | minified | gzip -9 | brotli -11 |', + '|---|---|---|---|', + ...rows, + ].join('\n'), + ); + return `baseline ${kib(base.gzip)} gzip; see the size table`; + }, 'vite-react19': (app) => { run('npm', ['run', 'build'], app); return scanClientBundle(join(app, 'dist')); @@ -124,5 +173,9 @@ try { const table = ['| fixture | result | notes |', '|---|---|---|', ...results.map((r) => `| ${r.name} | ${r.ok ? 'pass' : '**fail**'} | ${r.note} |`)].join('\n'); console.log(`\n${table}`); -if (process.env.GITHUB_STEP_SUMMARY) appendFileSync(process.env.GITHUB_STEP_SUMMARY, `### Bundlers\n\n${table}\n`); +for (const t of sizeTables) console.log(`\n${t}`); +if (process.env.GITHUB_STEP_SUMMARY) { + appendFileSync(process.env.GITHUB_STEP_SUMMARY, `### Bundlers\n\n${table}\n`); + for (const t of sizeTables) appendFileSync(process.env.GITHUB_STEP_SUMMARY, `\n### Bundle size\n\n${t}\n`); +} if (results.some((r) => !r.ok)) process.exit(1); From a004ea334d470aa9a4ebba82c414f81d16533435 Mon Sep 17 00:00:00 2001 From: Afzal Ahmad Date: Tue, 17 Nov 2026 15:54:35 +0100 Subject: [PATCH 2/2] Engine ^2.0.0-beta.0; beta wording javascript-excel 2.0.0-beta.0 is on npm. The library and the playground depend on ^2.0.0-beta.0, and the lockfile resolves it. The conformance corpus is unchanged at the beta.0 tag (sync --check passes). The README, the playground banner and the docs/api.md status line say that the 1.0 feature set is complete, and that changes before 1.0.0 are limited to fixes found in testing. --- .changeset/beta-wording.md | 5 +++++ .changeset/javascript-excel-alpha-7.md | 5 ----- .changeset/javascript-excel-beta-0.md | 5 +++++ README.md | 4 ++-- apps/playground/package.json | 2 +- apps/playground/src/App.tsx | 2 +- docs/api.md | 8 ++++---- docs/triage-1.0.md | 4 ++-- package-lock.json | 10 +++++----- packages/react-data-export/package.json | 2 +- 10 files changed, 26 insertions(+), 21 deletions(-) create mode 100644 .changeset/beta-wording.md delete mode 100644 .changeset/javascript-excel-alpha-7.md create mode 100644 .changeset/javascript-excel-beta-0.md diff --git a/.changeset/beta-wording.md b/.changeset/beta-wording.md new file mode 100644 index 0000000..15a2f58 --- /dev/null +++ b/.changeset/beta-wording.md @@ -0,0 +1,5 @@ +--- +"react-data-export": patch +--- + +README: the 1.0 feature set is complete; until 1.0.0, changes are limited to fixes found in testing. A Web Worker option comes in a 1.x release. diff --git a/.changeset/javascript-excel-alpha-7.md b/.changeset/javascript-excel-alpha-7.md deleted file mode 100644 index 53bf05e..0000000 --- a/.changeset/javascript-excel-alpha-7.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"react-data-export": patch ---- - -Depend on javascript-excel `^2.0.0-alpha.7`. Its writer returns to the event loop about every 16 ms, so a large `.xlsx` export on the main thread no longer freezes the page, and `signal`/`abort()` take effect while it runs. diff --git a/.changeset/javascript-excel-beta-0.md b/.changeset/javascript-excel-beta-0.md new file mode 100644 index 0000000..2cfc784 --- /dev/null +++ b/.changeset/javascript-excel-beta-0.md @@ -0,0 +1,5 @@ +--- +"react-data-export": patch +--- + +Depend on javascript-excel `^2.0.0-beta.0`, its first 2.0.0 beta. Since 2.0.0-alpha.7 its writer returns to the event loop about every 16 ms, so a large `.xlsx` export on the main thread no longer freezes the page, and `signal`/`abort()` take effect while it runs. diff --git a/README.md b/README.md index 87bcc3f..2a4b41e 100644 --- a/README.md +++ b/README.md @@ -5,8 +5,8 @@ Export data from React to `.xlsx` and `.csv`. ## Status: 1.0 is a from-scratch rewrite, in progress - **1.0 has a new API.** It is rebuilt on [javascript-excel](https://github.com/securedeveloper/javascript-excel) 2.0, and its main entry has no `` / `` / ``. The 0.6 API ships only as the deprecated `react-data-export/legacy` entry: supported for all of 1.x, removed in 2.0. See [Migrating from 0.x](#migrating-from-0x). -- **1.0 prereleases are on npm's `next` tag:** `npm install react-data-export@next`. They have dataset export (`exportDataset`, `exportWorkbook`, `useExcelExport`, ``) and table export for an HTML `` (`exportTable`, `useTableExport`, ``), as specified in [docs/api.md](docs/api.md), built on javascript-excel 2.0's `fromDataset`, `fromTable`, writer and download. As an alpha, the API may still change before 1.0.0. Coming from 0.x: the [migration guide](docs/migration.md). -- **Big exports stay responsive.** Exports run on the main thread. On javascript-excel 2.0.0-alpha.7 and later (the version react-data-export requires), the `.xlsx` writer returns to the event loop about every 16 ms, so the page keeps rendering and handling input during a large export, and `abort()` works while it runs. A `worker` option, which writes the file in a Web Worker on top of `javascript-excel/worker`, comes in a 1.x release after 1.0.0, not in 1.0 ([docs/api.md §7](docs/api.md#7-errors-abort-and-progress)). +- **1.0 prereleases are on npm's `next` tag:** `npm install react-data-export@next`. They have dataset export (`exportDataset`, `exportWorkbook`, `useExcelExport`, ``) and table export for an HTML `
` (`exportTable`, `useTableExport`, ``), as specified in [docs/api.md](docs/api.md), built on javascript-excel 2.0's `fromDataset`, `fromTable`, writer and download. The 1.0 feature set is complete: until 1.0.0, changes are limited to fixes found in testing. Coming from 0.x: the [migration guide](docs/migration.md). +- **Big exports stay responsive.** Exports run on the main thread. Since javascript-excel 2.0.0-alpha.7 (react-data-export requires 2.0.0-beta.0 or later), the `.xlsx` writer returns to the event loop about every 16 ms, so the page keeps rendering and handling input during a large export, and `abort()` works while it runs. A `worker` option, which writes the file in a Web Worker on top of `javascript-excel/worker`, comes in a 1.x release after 1.0.0, not in 1.0 ([docs/api.md §7](docs/api.md#7-errors-abort-and-progress)). ```tsx import { ExcelExport } from 'react-data-export'; diff --git a/apps/playground/package.json b/apps/playground/package.json index 18107eb..f11db9b 100644 --- a/apps/playground/package.json +++ b/apps/playground/package.json @@ -10,7 +10,7 @@ "test": "vitest run" }, "dependencies": { - "javascript-excel": "^2.0.0-alpha.7", + "javascript-excel": "^2.0.0-beta.0", "react": "^19.3.1", "react-data-export": "1.0.0-alpha.3", "react-dom": "^19.3.1" diff --git a/apps/playground/src/App.tsx b/apps/playground/src/App.tsx index f0d408d..287f795 100644 --- a/apps/playground/src/App.tsx +++ b/apps/playground/src/App.tsx @@ -275,7 +275,7 @@ export function App(): ReactElement { return ( <>
diff --git a/docs/api.md b/docs/api.md index d026279..ebbcb3d 100644 --- a/docs/api.md +++ b/docs/api.md @@ -1,6 +1,6 @@ # react-data-export 1.0: API design (dataset module) -Status: **design decided (2026-11-16); the dataset module is implemented** (RDE-1.9) on **javascript-excel ≥ 2.0.0-alpha.7** (see [§9](#9-dependencies-and-order)), and ships in the 1.0 prereleases on npm's `next` tag. Table export (module B, [§13](#13-table-export)) is designed and implemented in RDE-1.17. +Status: **design decided (2026-11-16); the dataset module is implemented** (RDE-1.9) on **javascript-excel ≥ 2.0.0-beta.0** (see [§9](#9-dependencies-and-order)), and ships in the 1.0 prereleases on npm's `next` tag. The 1.0 feature set is complete: until 1.0.0, changes are limited to fixes found in testing. Table export (module B, [§13](#13-table-export)) is designed and implemented in RDE-1.17. This document covers module A, **dataset export** (`exportDataset`, `exportWorkbook`, `useExcelExport`, ``), and module B, **table export** (`exportTable`, `useTableExport`, ``, [§13](#13-table-export)). @@ -263,7 +263,7 @@ export function ExcelExport(props: ExcelExportProps): ReactElement; - react-data-export's own misuse errors (CSV with several sheets, `dataset` and `workbook` both or neither, an unknown `format`) are `TypeError`s. That's how javascript-excel treats invalid options too. - **Abort.** `signal` reaches `toBlob`, which checks it between sheet chunks. It is also checked before building and before the download starts. Every export starts by yielding once (one microtask) and re-checking the signal before it builds anything. `toCsvBlob` is synchronous, so without that yield a CSV export started in an effect would finish, download included, before React 18/19 StrictMode's simulated unmount could abort it, and the documented auto-export recipe would save the file twice in development. An abort rejects with `signal.reason` (a `DOMException` `AbortError` by default). `toCsvBlob` is synchronous, so a CSV export can only be aborted before it starts. - **Progress.** `onProgress` receives javascript-excel's `Progress` (`phase`, `sheet`, `ratio` from 0 to 1, non-decreasing) from `toBlob`. The building phase (`fromDataset`) is synchronous and reports nothing, so the first progress event comes from the writer. CSV reports no progress. -- **Big data: the main thread stays responsive.** In 1.0, exports run on the main thread. From javascript-excel 2.0.0-alpha.7 (the lowest version react-data-export depends on, §9), `toBlob` returns to the event loop about every 16 ms while it writes. So a large `.xlsx` export doesn't freeze the page: frames render, input is handled, and `abort()` or an aborted `signal` takes effect while the file is being written. The output bytes are the same as without the pauses. Building the sheet (`fromDataset`, `fromTable`) and writing CSV (`toCsvBlob`) are still synchronous. +- **Big data: the main thread stays responsive.** In 1.0, exports run on the main thread. From javascript-excel 2.0.0-alpha.7 (react-data-export depends on 2.0.0-beta.0 or later, §9), `toBlob` returns to the event loop about every 16 ms while it writes. So a large `.xlsx` export doesn't freeze the page: frames render, input is handled, and `abort()` or an aborted `signal` takes effect while the file is being written. The output bytes are the same as without the pauses. Building the sheet (`fromDataset`, `fromTable`) and writing CSV (`toCsvBlob`) are still synchronous. - **Worker: 1.x, not 1.0** (decided 2026-11-17). javascript-excel's worker entry, `javascript-excel/worker` (its §5.5), has existed since 2.0.0-alpha.1. react-data-export adds it after 1.0.0, in a 1.x minor release: - `fromDataset` and `fromTable` have to run on the main thread: accessors are functions and can't be sent to a worker, and the table is in the page. - The resulting sheet is plain data, and can be written in a worker. @@ -291,7 +291,7 @@ export function ExcelExport(props: ExcelExportProps): ReactElement; | `toBlob` returning to the event loop while it writes (§7) | core entry, §5.1 | 2.0.0-alpha.7 | | `WorkerClient` (1.x only, §7) | `javascript-excel/worker`, §5.5 | 2.0.0-alpha.1 (JSE-8) | -So react-data-export depends on `"javascript-excel": "^2.0.0-alpha.7"` ([Q6](#12-design-decisions)). 2.0.0-alpha.2 was the first prerelease with `fromDataset`/`fromDatasets`, and 2.0.0-alpha.7 is the first whose writer yields to the browser. Nothing in react-data-export reimplements them. +So react-data-export depends on `"javascript-excel": "^2.0.0-beta.0"` ([Q6](#12-design-decisions)), the first 2.0.0 beta. 2.0.0-alpha.2 was the first prerelease with `fromDataset`/`fromDatasets`, and 2.0.0-alpha.7 the first whose writer yields to the browser. Nothing in react-data-export reimplements them. ## 10. Feature coverage @@ -341,7 +341,7 @@ These were the open questions of the review. Each one is decided, and the sectio **Q5. `` triggers.** Decided (2026-11-16): a default button or a render prop, with no `cloneElement` (§6). The 0.x-style `element` with an injected `onClick` is not carried over, because it breaks with components that don't forward `onClick` and with fragments. -**Q6. javascript-excel range during the 2.0 prereleases.** Decided (2026-11-16): a caret range on a prerelease, `"javascript-excel": "^2.0.0-alpha.2"` at the time and `^2.0.0-alpha.7` now (§9). A caret on a prerelease matches only later 2.0.0 prereleases and 2.0.0 itself. An exact pin bumped with each alpha was not taken. +**Q6. javascript-excel range during the 2.0 prereleases.** Decided (2026-11-16): a caret range on a prerelease, `"javascript-excel": "^2.0.0-alpha.2"` at the time and `^2.0.0-beta.0` now (§9). A caret on a prerelease matches only later 2.0.0 prereleases and 2.0.0 itself. An exact pin bumped with each alpha was not taken. **Q7. Accessor fields.** Decided (2026-11-16): javascript-excel's `key` / `path` / `value` / `index` pass through unchanged (§3). That gives one documented shape for every framework and no ambiguity about `'a.b'`. A combined react-data-export field mapped to `key` or `path`, which javascript-excel's Q18 would allow, was not taken. diff --git a/docs/triage-1.0.md b/docs/triage-1.0.md index 1786495..abd9523 100644 --- a/docs/triage-1.0.md +++ b/docs/triage-1.0.md @@ -96,7 +96,7 @@ Thanks to the community pull requests whose ideas shaped 1.0: | #85 | Error by importing the project | Fixed in 1.0.0-alpha.1 | No `tempa-xlsx`, `xlsx`, `file-saver` or `prop-types` any more; the only dependency is javascript-excel (no runtime deps). Import errors from the old dependency chain can't happen. | | #90 | issue in react js dependence added time Module not found: Can't resolve 'react-data-export' using | Fixed in 1.0.0-alpha.1 | Same: the 0.x dependency chain is gone; `exports` map with ESM + CJS + types, smoke-tested from the packed tarball in CI. | | #100 | Module not found: Can't resolve 'prop-types' in \node_modules\react-data-export\dist\ExcelPlugin\components | Fixed in 1.0.0-alpha.1 | `prop-types` is not used in 1.0. | -| #110 | xlsx dependency blows up webpack bundle size | Fixed in 1.0.0-alpha.1 | `xlsx`/`tempa-xlsx` are no longer dependencies; javascript-excel has zero runtime dependencies and per-entry tree-shaking (writer, CSV, DOM are separate entries). Bundle size, measured with the bundler matrix's `bundle-size` fixture (`npm run bundlers -- bundle-size`: Vite 8.3.8 + React 19.3.1 production builds, react-data-export 1.0.0-alpha.3 on javascript-excel 2.0.0-alpha.7, minus the same app with React alone). `exportDataset` adds 72.8 KiB minified (24.7 KiB gzip), `` 78.4 KiB (27.7 KiB gzip), every export of the main entry 90.0 KiB (31.5 KiB gzip). 0.6.0's `` adds 741.1 KiB (266.3 KiB gzip). | +| #110 | xlsx dependency blows up webpack bundle size | Fixed in 1.0.0-alpha.1 | `xlsx`/`tempa-xlsx` are no longer dependencies; javascript-excel has zero runtime dependencies and per-entry tree-shaking (writer, CSV, DOM are separate entries). Bundle size, measured with the bundler matrix's `bundle-size` fixture (`npm run bundlers -- bundle-size`: Vite 8.3.8 + React 19.3.1 production builds, react-data-export 1.0.0-alpha.3 on javascript-excel 2.0.0-alpha.7 and 2.0.0-beta.0, which give the same numbers, minus the same app with React alone). `exportDataset` adds 72.8 KiB minified (24.7 KiB gzip), `` 78.4 KiB (27.7 KiB gzip), every export of the main entry 90.0 KiB (31.5 KiB gzip). 0.6.0's `` adds 741.1 KiB (266.3 KiB gzip). | | #168 | Module not found can't resolve 'fs' in node_modules\tempa-xlsx | Fixed in 1.0.0-alpha.1 | No `tempa-xlsx`, so no `fs` import; covered by the CRA/webpack 5 fixture in the bundler matrix (RDE-1.11). | | #169 | Why does xlsx get installed into my package.json when installing this package | Fixed in 1.0.0-alpha.1 | `xlsx` is not a dependency or a required peer in 1.0. | | #173 | Application crash when using vitejs | Fixed in 1.0.0-alpha.1 | No `cptable`/`xlsx` code; Vite fixture in the bundler matrix. | @@ -218,7 +218,7 @@ Thanks to the community pull requests whose ideas shaped 1.0: | # | title | disposition | how / reason | |---|---|---|---| | #154 | The maximum you can export to excel is 1299 rows, how to increase the number of exported rows? | Fixed in 1.0.0-alpha.1 | Measured on alpha.1 (Node 24): 1,300 / 10,000 / 100,000 rows × 3 columns export and read back complete (100k rows: 318 ms, 2.1 MB). | -| #170 | Browser window stops responding | Still open, tracked | From javascript-excel 2.0.0-alpha.7, which react-data-export requires, the writer returns to the event loop about every 16 ms, so a large export on the main thread no longer freezes the page. The `worker` option (`javascript-excel/worker`) lands in react-data-export 1.x, not 1.0 (decided 2026-11-17). Keep open until the worker option ships. | +| #170 | Browser window stops responding | Still open, tracked | From javascript-excel 2.0.0-alpha.7 (react-data-export requires 2.0.0-beta.0 or later), the writer returns to the event loop about every 16 ms, so a large export on the main thread no longer freezes the page. The `worker` option (`javascript-excel/worker`) lands in react-data-export 1.x, not 1.0 (decided 2026-11-17). Keep open until the worker option ships. | ### Out of scope for 1.0 diff --git a/package-lock.json b/package-lock.json index f6eb414..42a5720 100644 --- a/package-lock.json +++ b/package-lock.json @@ -21,7 +21,7 @@ }, "apps/playground": { "dependencies": { - "javascript-excel": "^2.0.0-alpha.7", + "javascript-excel": "^2.0.0-beta.0", "react": "^19.3.1", "react-data-export": "1.0.0-alpha.3", "react-dom": "^19.3.1" @@ -2188,9 +2188,9 @@ "license": "MIT" }, "node_modules/javascript-excel": { - "version": "2.0.0-alpha.7", - "resolved": "https://registry.npmjs.org/javascript-excel/-/javascript-excel-2.0.0-alpha.7.tgz", - "integrity": "sha512-Vgehcr5hl/jqxhuE2Mh0F7VeKrl0DdjdYgmT2RIAFfxY9ecYm3ZCY15ohOpU/gKaWzZgH7ELxgtwR8OxS3CjCA==", + "version": "2.0.0-beta.0", + "resolved": "https://registry.npmjs.org/javascript-excel/-/javascript-excel-2.0.0-beta.0.tgz", + "integrity": "sha512-TYYjCNaG/qWaUV6TS3yDMWn/awxxH722sX6Hr67XmFrJaasf2w/VQO/2BsBvwfG0KXuGTal0dUdg2hN/UqSezg==", "license": "MIT", "engines": { "node": ">=22" @@ -4156,7 +4156,7 @@ "version": "1.0.0-alpha.3", "license": "MIT", "dependencies": { - "javascript-excel": "^2.0.0-alpha.7" + "javascript-excel": "^2.0.0-beta.0" }, "devDependencies": { "@arethetypeswrong/cli": "^0.18.5", diff --git a/packages/react-data-export/package.json b/packages/react-data-export/package.json index 0b1bf39..45c0eef 100644 --- a/packages/react-data-export/package.json +++ b/packages/react-data-export/package.json @@ -80,6 +80,6 @@ "vitest": "^5.1.0" }, "dependencies": { - "javascript-excel": "^2.0.0-alpha.7" + "javascript-excel": "^2.0.0-beta.0" } }