-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate WASM lib #62
Conversation
project shouldn't have two locks files. removing yarn.lock because we seem to be using package-lock.json more commonly in the context of tss.
- revise client lib for easier upgrading through usage of wasm-pack with --omit-default-module-path - add tss-lib-wasm package that separately holds the wasm file. this allows loading the wasm from a package on demand and keeping the size of tss-lib low.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May have reviewed this prematurely.
There are some good things about this PR, however some of the deletions need to be checked.
Please add a PR to dkls for this with updated build instructions this as well. |
Thanks for the reminder! 🙏 |
added tests and ci as well |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
This PR proposes a refactor of the WASM lib.
Background: We want to have the same interface for FROST and DKLS libs, so that they can be integrated easily within MPC Core Kit. WASM should be packaged separately, so that we can keep size of core kit bundle low.