We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initializing duckdb_blocking throws an undefined (reading 'mainModule') error.
To resolve it, I had to do this.
let db = await duckdb_blocking.createDuckDB( **{ eh: DUCKDB_BUNDLES },** logger, duckdb_blocking.BROWSER_RUNTIME );
The issue should stem from here where it checks if the bundles.eh exists.
bundles.eh
duckdb-wasm/packages/duckdb-wasm/src/targets/duckdb-browser-blocking.ts
Line 23 in b4d2182
I created a sandbox here: https://codesandbox.io/p/sandbox/bold-goldwasser-cgzhvv
import * as duckdb from "@duckdb/duckdb-wasm"; import * as duckdb_blocking from "@duckdb/duckdb-wasm/blocking"; async function instantiate(duckdb) { const JSDELIVR_BUNDLES = duckdb.getJsDelivrBundles(); const DUCKDB_BUNDLES = await duckdb.selectBundle(JSDELIVR_BUNDLES); const logger = new duckdb_blocking.VoidLogger(); let db = await duckdb_blocking.createDuckDB( **DUCKDB_BUNDLES**, logger, duckdb_blocking.BROWSER_RUNTIME ); await db.instantiate((_) => {}); return db; }
Chrome
macOS
1.28.0
browser
seeya
None
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happens?
Initializing duckdb_blocking throws an undefined (reading 'mainModule') error.
To resolve it, I had to do this.
The issue should stem from here where it checks if the
bundles.eh
exists.duckdb-wasm/packages/duckdb-wasm/src/targets/duckdb-browser-blocking.ts
Line 23 in b4d2182
To Reproduce
I created a sandbox here: https://codesandbox.io/p/sandbox/bold-goldwasser-cgzhvv
Browser/Environment:
Chrome
Device:
macOS
DuckDB-Wasm Version:
1.28.0
DuckDB-Wasm Deployment:
browser
Full Name:
seeya
Affiliation:
None
The text was updated successfully, but these errors were encountered: