-
Notifications
You must be signed in to change notification settings - Fork 17
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
@penumbra-zone/wasm
#955
@penumbra-zone/wasm
#955
Conversation
ah, wasm-pack creates a gitignore |
@penumbra-zone/keys
and @penumbra-zone/wasm
2516169
to
a48b39b
Compare
@penumbra-zone/keys
and @penumbra-zone/wasm
@penumbra-zone/wasm
a48b39b
to
49da696
Compare
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.
Nice job! After this is merged, the bot will update this PR: #940. Then if you merge that, this will publish to npm for the consumer needing this.
Also, could you add documentation to a README.md on how to use this package? Think it would be helpful to give instructions on:
- No keys usage
- Usage w/ keys (and downloading that optional package)
- Possible required webpack/next configs
49da696
to
745ee92
Compare
work on #737
the wasm package on npm is outdated, and we have consumers trying to use, so i took a shot at this
keys package
@penumbra-zone/keys
#958wasm package
verified working on an example nextjs app with the output of
pnpm pack
which you can view at https://github.com/turbocrime/nextjs-penumbra-wasm-example/