feat: publish xlsx import export as separate wasm

Author: BrianHung

.github/workflows/rust-build-test.yaml

@@ -18,6 +18,12 @@ jobs:
 
             - name: Install wasm-pack
               run: curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh
+           
+            - name: Install wasm-bindgen-cli
+              run: cargo install -f wasm-bindgen-cli --version 0.2.100
+            
+            - name: Add wasm32 target
+              run: rustup target add wasm32-unknown-unknown
 
             - name: Build
               run: cargo build --release --verbose

.gitignore

@@ -1,3 +1,4 @@
 target/*
 **/node_modules/**
 .DS_Store
+bindings/wasm/pkg/

Cargo.lock

@@ -1,7 +1,8 @@
 .PHONY: lint
 lint:
 	cargo fmt -- --check
-	cargo clippy --all-targets --all-features -- -W clippy::unwrap_used -W clippy::expect_used -W clippy::panic -D warnings
+	cargo clippy --workspace --exclude wasm --all-targets --all-features -- -W clippy::unwrap_used -W clippy::expect_used -W clippy::panic -D warnings
+	cd bindings/wasm/ && cargo clippy --target wasm32-unknown-unknown -- -W clippy::unwrap_used -W clippy::expect_used -W clippy::panic -D warnings
 	cd webapp/IronCalc/ && npm install && npm run check
 	cd webapp/app.ironcalc.com/frontend/ && npm install && npm run check
 
@@ -15,7 +16,12 @@ tests: lint
 	make remove-artifacts
 	# Regretabbly we need to build the wasm twice, once for the nodejs tests
 	# and a second one for the vitest.
-	cd bindings/wasm/ && wasm-pack build --target nodejs && node tests/test.mjs && make
+	cd bindings/wasm/ && \
+	  wasm-pack build --target nodejs --out-name ironcalc && \
+	  cargo build --release --target wasm32-unknown-unknown --bin xlsx_wasm && \
+	  wasm-bindgen --target nodejs --typescript --out-dir pkg --out-name xlsx ../../target/wasm32-unknown-unknown/release/xlsx_wasm.wasm && \
+	  node tests/test.mjs && \
+	  make
 	cd webapp/IronCalc/ && npm run test
 	cd bindings/python && ./run_tests.sh && ./run_examples.sh
 

Makefile

@@ -8,17 +8,19 @@ repository = "https://github.com/ironcalc/ironcalc"
 edition = "2021"
 
 [lib]
+name = "ironcalc_wasm"
 crate-type = ["cdylib"]
 
+[[bin]]
+name = "xlsx_wasm"
+path = "src/xlsx.rs"
+
 [dependencies]
-# Uses `../ironcalc/base` when used locally, and uses
-# the inicated version from crates.io when published.
-# https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#multiple-locations
 ironcalc = { path = "../../xlsx", version = "0.5.0" }
 ironcalc_base = { path = "../../base", version = "0.5", features = ["use_regex_lite"] }
 serde = { version = "1.0", features = ["derive"] }
-wasm-bindgen = "0.2.92"
-serde-wasm-bindgen = "0.4"
+wasm-bindgen = "0.2.100"
+serde-wasm-bindgen = "0.6"
 
 [dev-dependencies]
-wasm-bindgen-test = "0.3.38"
+wasm-bindgen-test = "0.3.38"

bindings/wasm/Cargo.toml

@@ -1,3 +1,20 @@
+# ---------------------------------------------------------------------------
+# Build strategy
+# ---------------------------------------------------------------------------
+# We need two separate WASM bundles in the same NPM package:
+#   1) Core engine  →  @ironcalc/wasm            (small, always shipped)
+#   2) XLSX helpers →  @ironcalc/wasm/xlsx       (large, optional)
+#
+# The natural way would be two wasm-pack invocations – one default lib and one
+#   wasm-pack build --bin xlsx_wasm …
+# Unfortunately, on the stable Rust tool-chain wasm-pack's `--bin` flag relies
+# on Cargo's unstable `--out-dir`/`--artifact-dir` feature and therefore fails.
+#
+# Until that becomes stable (or we switch to a nightly tool-chain), we compile
+# the second binary with plain `cargo build` and then run `wasm-bindgen`
+# ourselves.  As soon as the flag is stabilised we can collapse back to the
+# two simple wasm-pack commands shown above and delete the hand-rolled steps.
+# ---------------------------------------------------------------------------
 # In some platforms, python is called python3
 PYTHON := $(shell command -v python 2>/dev/null || command -v python3 2>/dev/null)
 
@@ -6,15 +23,35 @@ ifeq ($(PYTHON),)
   $(error No python found. Please install python.)
 endif
 
+TEMP_DIR := pkg_xlsx
+
 all:
-	wasm-pack build --target web --scope ironcalc --release
+	wasm-pack build --target web --scope ironcalc --out-dir pkg --out-name ironcalc --release
+
+	# Build XLSX helper separately (cargo + wasm-bindgen)
+	cargo build --release --target wasm32-unknown-unknown --bin xlsx_wasm
+	wasm-bindgen --target web --typescript --out-dir $(TEMP_DIR) --out-name xlsx ../../target/wasm32-unknown-unknown/release/xlsx_wasm.wasm
+
+	# Move generated files into main pkg directory
+	mv $(TEMP_DIR)/xlsx_bg.wasm pkg/xlsx_bg.wasm
+	mv $(TEMP_DIR)/xlsx.js pkg/xlsx.js
+	mv $(TEMP_DIR)/xlsx.d.ts pkg/xlsx.d.ts
+
 	cp README.pkg.md pkg/README.md
 	npx tsc types.ts --target esnext --module esnext
 	$(PYTHON) fix_types.py
 	rm -f types.js
+	rm -rf $(TEMP_DIR)
 
 tests:
-	wasm-pack build --target nodejs && node tests/test.mjs
+	wasm-pack build --target nodejs --out-dir pkg --out-name ironcalc
+	cargo build --release --target wasm32-unknown-unknown --bin xlsx_wasm
+	wasm-bindgen --target nodejs --typescript --out-dir $(TEMP_DIR) --out-name xlsx ../../target/wasm32-unknown-unknown/release/xlsx_wasm.wasm
+	mv $(TEMP_DIR)/xlsx_bg.wasm pkg/xlsx_bg.wasm || true
+	mv $(TEMP_DIR)/xlsx.js pkg/xlsx.js || true
+	mv $(TEMP_DIR)/xlsx.d.ts pkg/xlsx.d.ts || true
+	rm -rf $(TEMP_DIR)
+	node tests/test.mjs
 
 lint:
 	cargo check

bindings/wasm/Makefile

@@ -1,6 +1,7 @@
 # IronCalc Web bindings
 
-This package contains web bindings for IronCalc. It exposes the engine and helper functions to import or export workbooks as XLSX or IronCalc (icalc) byte arrays. The built-in XLSX support focuses on core spreadsheet features like cell values, formulas, and styling.
+This crate is used to build the web bindings for IronCalc.
+Note that it does not contain the xlsx writer and reader, only the engine.
 
 https://www.npmjs.com/package/@ironcalc/wasm?activeTab=readme
 

bindings/wasm/README.md

@@ -1,7 +1,6 @@
 # IronCalc Web bindings
 
-This package contains web bindings for IronCalc. It exposes the engine and helper functions to import or export workbooks as XLSX or IronCalc (icalc) byte arrays. The built-in XLSX support focuses on core spreadsheet features like cell values, formulas, and styling.
-
+This crate is used to build the web bindings for IronCalc.
 
 ## Usage
 
@@ -15,8 +14,11 @@ And then in your TypeScript
 
 ```TypeScript
 import init, { Model } from "@ironcalc/wasm";
+import initXLSX, { toXLSXBytes, fromXLSXBytes } from "@ironcalc/wasm/xlsx";
+
 
 await init();
+await initXLSX();
 
 function compute() {
     const model = new Model('en', 'UTC');
@@ -30,23 +32,15 @@ function compute() {
 }
 
 compute();
-```
-
-### Importing and exporting bytes
-
-The `Model` class provides helpers to load or save workbooks as raw byte arrays.
 
-```ts
 // create a new workbook and export as XLSX bytes
 const model = new Model('Workbook1', 'en', 'UTC');
 model.setUserInput(0, 1, 1, '42');
-const xlsxBytes = model.saveToXlsx();
+const xlsxBytes = toXLSXBytes(model.toBytes());
 
 // load from those bytes
-const roundTripped = Model.fromXlsxBytes(xlsxBytes, 'Workbook1', 'en', 'UTC');
+const roundTrippedBytes = fromXLSXBytes(xlsxBytes, 'Workbook1', 'en', 'UTC');
+const roundTripped = Model.fromBytes(roundTrippedBytes);
 
-// same helpers exist for IronCalc's internal format
-const icalcBytes = model.saveToIcalc();
-const restored = Model.fromIcalcBytes(icalcBytes);
 ```