Using DuckDB WASM without a Worker

[sswatson]

I'm looking to use DuckDB in a Chrome extension, and it works great if I load DuckDB WASM in the bundle for the extension popup. However, the popup environment is transient, so that approach involves a lot of serialization and deserialization. So it would be much nicer if I could move the DuckDB execution into the background script.

On the other hand, the background script in a Chrome extension doesn't have access to the Worker API, so I can't do const worker = new Worker(bundle.mainWorker); db = new duckdb.AsyncDuckDB(logger, worker); as one usually does in the instantiation boilerplate in the README.

So my question is: is it possible to use DuckDB WASM in an environment where you don't have access to the Worker class?

[carlopi]

I think this should be workable, modelling this after the node environment where duckdb-wasm is executed directly in the main thread, but there is some refactoring needed to match functionality.

The specific problem you are tackling might be significantly simpler if you know what's a minimal set of functionality you would need you can try embed directly duckdb-browser-eh.js and then build the API you need to access the lower level functions.

[sswatson]

Thanks for the reply! Where might I be able to find the node environment example showing how duckdb-wasm can be used directly in the main thread? The Node examples in the examples directory seem to use workers.

[jlarmstrongiv]

I am also trying to run duckdb-wasm in an environment without web workers.

@sswatson and @carlopi were either of you able to find or create an example using duckdb-wasm without web workers?

[sswatson]

I was not. I ended up sticking with my original setup.