Skip to content

Publish browser-ready WASM packages and SDK entrypoints - #2

Open
i001962 wants to merge 1 commit into
QuilibriumNetwork:masterfrom
i001962:codex/fix-browser-package
Open

Publish browser-ready WASM packages and SDK entrypoints#2
i001962 wants to merge 1 commit into
QuilibriumNetwork:masterfrom
i001962:codex/fix-browser-package

Conversation

@i001962

@i001962 i001962 commented Aug 27, 2026

Copy link
Copy Markdown

Note

This patch was generated with AI assistance and is offered as a proposed approach, not an official Quilibrium SDK fix. It was created to unblock our development while we wait for the Quilibrium team to publish its canonical patch.

Summary

  • turn the repository root into a private monorepo package and publish the actual vanilla SDK as @quilibrium/qkms-sdk@2.1.1
  • add publishable scoped packages for DKLs23, channel, BLS48-581, Bulletproofs, and MPC WASM artifacts
  • add conditional browser/Node exports with browser-safe ESM loaders and no filesystem shims in browser bundles
  • replace local ceremonyclient file dependencies with workspace/package dependencies and a reproducible upstream Go module reference
  • remove Vite/Next workarounds and add a clean packed-consumer smoke test that installs all nine tarballs

Testing

  • pnpm test (30 tests)
  • pnpm test:package (packs and installs all nine packages, initializes Node runtimes, and builds a clean Vite consumer with all five WASM assets)
  • ./test.sh all (SigV4, FROST, BLS48, BLS12, and RSA protocol smoke tests; 6/6)
  • ./test.sh wasm (4/4)
  • pnpm --dir examples/qkms-next-starter build
  • pnpm --dir examples/qkms-react-starter build
  • pnpm --dir examples/qkms-vanilla-starter build

Fixes #1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

npm install does not give us a normal resolvable browser/node package for dkls23wasm et al

1 participant