rivet-dev / rivet-dev/dynamic-apps
@agentos-software/duckdb: wasm build unimplemented (CMake→wasm), blocks publish
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 51
- Avg merge
- 6m
- Merged PRs (30d)
- 13
Description
@agentos-software/duckdb is unpublished — it has no wasm build, so it's skipped by registry/publish-software.sh:
case "$n" in wget|duckdb|make|build-essential) ... duckdb - skipped (heavy CMake->wasm build)
Problem: duckdb needs a heavy CMake→wasm32-wasip1 build that isn't wired up, so no .wasm is produced and the package has no dist/index.js to publish (versions: [] on npm).
Impact: agent-os packages/shell depended on @agentos-software/duckdb; since it can't resolve, it was dropped from packages/shell to unblock agent-os CI. Re-add once the wasm build lands.
Done when: duckdb builds to wasm32-wasip1, publish-software.sh no longer excludes it, the package publishes, and it's restored to agent-os packages/shell.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with registry/publish-software.sh and the @agentos-software/duckdb package, then inspect how its CMake build is currently handled. Done means producing a wasm32-wasip1 build and dist/index.js, removing duckdb from the publish exclusion, publishing the package, and restoring it to agent-os packages/shell.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript, wasm
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100