Skip to content

feat(wasm): add a dedicated zstd entry point - #252

Draft
BridgeAR wants to merge 2 commits into
mainfrom
BridgeAR/2026-09-03-wasm-zstd-split
Draft

feat(wasm): add a dedicated zstd entry point#252
BridgeAR wants to merge 2 commits into
mainfrom
BridgeAR/2026-09-03-wasm-zstd-split

Conversation

@BridgeAR

@BridgeAR BridgeAR commented Sep 3, 2026

Copy link
Copy Markdown
Member

Builds Zstandard compression as a separate WASM crate and exposes typed CJS and ESM subpaths. The root API remains compatible through a lazy wrapper.

The direct entry point is 29,989 JavaScript bytes instead of 227,604, reducing loaded code by 86.8%. The published package grows by about 28 KiB.

Tested with the complete 49-test package and type suite, dependency validation, Clippy, and ESLint.

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

Overall package size

Self size: 31.53 MB
Deduped: 31.53 MB
No deduping: 31.53 MB

Dependency sizes | name | version | self size | total size | |------|---------|-----------|------------|

🤖 This report was automatically generated by heaviest-objects-in-the-universe

Consumers that only need Zstandard compression currently load the exporter, DDSketch, and their transitive Rust code. Build compression as a separate WASM crate and expose it through a typed subpath while keeping the root API as a lazy compatibility wrapper.

The direct entry point is 29,989 JavaScript bytes instead of 227,604 (86.8% less loaded code). The package grows by about 28 KiB so existing consumers remain compatible.
@BridgeAR
BridgeAR force-pushed the BridgeAR/2026-09-03-wasm-zstd-split branch from 055b23c to d0ae57d Compare September 3, 2026 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant