Skip to content
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

Build/pull Clarity REPL when building the book #36

Open
MarvinJanssen opened this issue Jan 15, 2023 · 8 comments · May be fixed by #58
Open

Build/pull Clarity REPL when building the book #36

MarvinJanssen opened this issue Jan 15, 2023 · 8 comments · May be fixed by #58

Comments

@MarvinJanssen
Copy link
Member

MarvinJanssen commented Jan 15, 2023

When the build script was originally put together, it was not straightforward to build the latest clarity-repl WASM binary. The script therefore pulls an old version from a CDN. It should instead grab the latest from here: https://github.com/hirosystems/clarinet/tree/develop/components/clarity-repl

@friedger
Copy link
Contributor

Update to clarity wasm. Could you help, @obycode ?

@obycode
Copy link
Contributor

obycode commented Dec 26, 2023

The clarity-wasm work can't yet be compiled to wasm itself, but Clarinet is using a wasm build of the repl with the current interpreter. Maybe @hugocaillard could help find an easy way to publish this module in Clarinet's CI?

@MarvinJanssen
Copy link
Member Author

Would be amazing if the book can get some love on the WASM front!

@friedger
Copy link
Contributor

Can we just use the clarinet sdk? using simnet.runSnippet('(int-to-ascii u1)')

@hugocaillard
Copy link

@friedger
The sdk as it is published on npm only works with Node.js. But in the past week, I've been working on a POC that works in the browser.
I'm not sure I'll be able to publish an universal package (for node and the browser), but I could get something like @hirosystems/clarinet-sdk-browser pretty soon

@friedger
Copy link
Contributor

@hugocaillard That would be amazing.

@MarvinJanssen
Copy link
Member Author

@hugocaillard +1 sounds amazing.

@hugocaillard
Copy link

hugocaillard commented May 3, 2024

@MarvinJanssen @friedger Proposal here #51

@friedger friedger linked a pull request May 27, 2024 that will close this issue
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 a pull request may close this issue.

4 participants