author	updated_on
hangxingliu	2025-04-21 23:58:41 -0700

DuckDB-Wasm

Publish the New Version

Build all WASM files in your duckdb WASM project:

cd ../duckdb-wasm
./scripts/datadocs_release_build_all.sh

Then, sync all required files into the package in this project:

./scripts/rsync.sh ../duckdb-wasm

Test the new WASM files and code in this project:

yarn install
yarn start

Then, please make sure the GITHUB_TOKEN env variable has been set or you can define it in the .env file at the root of this project. (You can read the next sub-section to learn more about this token)

Finally, use the following command to publish the package if there are no issues in above test step:

./scripts/release-new-version.sh
# or:
# cd duckdb-wasm && yarn version patch && yarn npm publish --access public

Create a GITHUB_TOKEN for Publishing

Visit the token creation page: https://github.com/settings/tokens/new

Enter a personal note you want and choose an appropriate expiration time. Then select only the following scopes:

• write:packages
• read:packages

Note

Github has not supported package scopes in their new fine-grained PAT: Packages support for fine-grained PATs #558 @github/roadmap

Link to Other Projects

cd /path/to/other-project
yarn link /path/to/this-project/duckdb-wasm

Links

• DuckDB WASM official repo: https://github.com/duckdb/duckdb-wasm
• Datadocs forked repo: https://github.com/datadocs/duckdb-wasm