It should be better to write npm i @duckdb/duckdb-wasm@next to the doc because @duckdb/duckdb-wasm@latest is too old and not compatible with duckdb@latest

[Narazaka]

Because I fell into the trap and wrote bitter words on SNS.

[domoritz]

I think instead a new release would be better.

[carlopi]

New release has to be.
I was doing some more serious testing, one problem I am aware of in current main is that multithreaded is at the moment broken, due to API changes Emscripten side that we need to adapt to. This affects only coi target, unsure if that's a blocker or given situation release is still better.

[carlopi]

I am trying to fix that, then another round of testing and marking a release.