Repository navigation
docs: worker option in 1.x; main-thread writer yields; engine ^2.0.0-beta.0 and beta wording; #110 bundle size measured - #214
Merged
Conversation
…script-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.
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.
securedeveloper
force-pushed
the
rde-docs-1x-worker
branch
from
November 17, 2026 14:54
8bbc3e9 to
a004ea3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the docs in line with the decision of 2026-11-17: the background-worker export lands in 1.x, not 1.0. Until then, the main-thread export yields to the browser (as of javascript-excel 2.0.0-alpha.7). This PR also moves the engine to javascript-excel's first beta, switches the wording to beta, and replaces the
[placeholder]for the #110 bundle size with measured numbers.Engine range
react-data-exportand the playground now depend onjavascript-excel@^2.0.0-beta.0(was^2.0.0-alpha.3). The lockfile moves from alpha.3 to beta.0.toBlobreturns to the event loop about every 16 ms while it writes, so a large.xlsxexport on the main thread no longer freezes the page, and an abort takes effect mid-write. The output bytes are unchanged.v2.0.0-beta.0tag, sonode scripts/sync-jse-corpus.mjs --checkpasses without a new copy. The Conformance job runs here..changeset/javascript-excel-beta-0.mdand.changeset/beta-wording.md.Beta wording
The README, the playground banner (
apps/playground/src/App.tsx) and the docs/api.md status line no longer say "alpha". They say that the 1.0 feature set is complete and that, until 1.0.0, changes are limited to fixes found in testing. The banner keeps showing{version}.Docs
worker?: WorkerClientoption comes in a 1.x minor release (decided 2026-11-17).javascript-excel/workerhas existed since 2.0.0-alpha.1, so the "planned (JSE-8)" wording in §9 was stale.^2.0.0-beta.0) and gains a row for the yielding writer (since alpha.7).Bundle size (#110)
There's a new
fixtures/bundle-sizefixture in the bundler matrix. It's not a compatibility check. It makes one Vite production build per usage and one with React alone, andscripts/bundlers.mjsprints what each usage adds (minified, gzip -9, brotli -11). The table goes to the log and theBundlersjob summary. The 1.0 builds also get the same no-fs/tempa-xlsx/jszipscan as the other fixtures.Measured locally on Node 26 with
npm run bundlers -- bundle-size: Vite 8.3.8 + React 19.3.1, react-data-export 1.0.0-alpha.3 (packed from this branch) on javascript-excel 2.0.0-alpha.7. CI's fresh install resolved 2.0.0-beta.0 and gave exactly the same numbers. The baseline, React alone, is 213.7 KiB minified (65.8 KiB gzip).exportDatasetbehind a button<ExportTableButton>on a table<ExcelFile>+<ExcelSheet>+<ExcelColumn>Dependencies
vite8.3.8,react/react-dom19.3.1, the same versions asvite-react19;react-data-export-0.6(an npm alias of[email protected]) for the comparison row;prop-types15.8.1, which 0.6.0 imports without declaring it ( Module not found: Can't resolve 'prop-types' in \node_modules\react-data-export\dist\ExcelPlugin\components #100).Local runs (Node 26), after the rebase onto main:
npm testwith openpyxl (204 passed, 2 skipped), the playground tests,npm run typecheckanddocs:checkpass, and so doesnpm run bundlers -- bundle-size.