Builtin Extensions

[johannesrue]

Hi at all!

At first, thank you very much for this great project and the effort you're putting in it.

I have an browser environment where i'd like to use duckdb-wasm with the following restrictions:

• No webserver
• No internet connection

So far so good, i got duckdb-wasm up and running.
Unfortunately i need the json and parquet extension which is loaded via an ajax request by default from extensions.duckdb.org.
This is a show stopper for me, so i started wondering if i could handover the extension files to duckdb somehow. But yet i have no solution, since i have no access to the FS of course and loading extensions via data url doesn't seem to work either (https://duckdb.org/docs/extensions/working_with_extensions#loading-extension-from-a-path).

So i stumbled upon this: #880
If i understand it correctly, this gives the option to make a duckdb-wasm build with e.g. a JSON extension builtin. Builtin means for me, at runtime there will no need to load the extension via a separate ajax call because the code comes with the duckdb.wasm.

If this is not the case, is there any other option to avoid the extension being separately loaded?

Nevertheless i tried my luck and started a build DUCKDB_JSON=1 make wasm with success (i believed).
Among others i got a duckdb-browser-mvp.worker.js and duckdb-mvp.wasm as a result.
But the first thing i wonder about is their size. There are much smaller compared to those shiped via npm. In the end they even don't work, because at runtime the i got the following error: dynCall_iiijj is not defined

Do you have any tips for me?

Thanks & cheers
Johannes

[johannesrue]

UPDATE: I was successful by using an older version (a4d06ae) which i more or less randomly picked. I'm not sure what's differnce which leads to the error in the compiled wasm.