Failure in tableToIPC when using a v21.0.0 apache-arrow version than the dependency

[VincenzoManto]

What happens?

When serializing a Table object from connection.query() using tableToIPC, the process fails silently if the imported apache-arrow version doesn't match the one duckdb-wasm depends on (e.g., using Arrow v21 with duckdb-wasm v1.30.0 which needs Arrow v17).
tableToIPC runs without errors, but tableFromIPC on the main thread produces an empty Table. This is difficult to debug as there is no explicit error.

To Reproduce

1. Use duckdb-wasm@1.30.0
2. Import apache-arrow@21.0.0 in the worker.
3. Execute a query to get a Table result.
4. Serialize the result with tableToIPC from v21.
5. Deserialize the result with tableFromIPC from v21.
6. Observe: The resulting table is empty.
7. Compare: Repeat with apache-arrow@17.0.0; the table deserializes correctly.

// A minimal test case
import * as duckdb from 'https://cdn.jsdelivr.net/npm/@duckdb/duckdb-wasm@1.30.0/+esm';
import { Table, tableToIPC, tableFromIPC } from 'https://cdn.jsdelivr.net/npm/apache-arrow@21.0.0/+esm'; // Fails
// import { Table, tableToIPC, tableFromIPC } from 'https://cdn.jsdelivr.net/npm/apache-arrow@17.0.0/+esm'; // Works

// ... (DB init) ...
const queryResult = await conn.query(`SELECT 1 AS a`);
const serialized = tableToIPC(new Table(queryResult.chunks));
const deserialized = tableFromIPC(serialized);
console.log(`Rows found: ${deserialized.numRows}`); // Logs 0 with v21, 1 with v17

Browser/Environment:

Chrome 139

Device:

HP Pavilion

DuckDB-Wasm Version:

1.30.0

DuckDB-Wasm Deployment:

worker

Full Name:

Vincenzo Manto

Affiliation:

None