lambdaclass
Wasm cairo integration
Because most of the codes in "Cairo by Example" are pure Cairo codes, adding an online playground for Cairo makes some sense. Of course, this playground used https://github.com/lambdaclass/cairo-vm.
You can see how it works.
or see this video.
Can you review this PR, sir? @unbalancedparentheses @MegaRedHand @juanbono @klaus993 @SantiagoPittella
We should, instead of having the binary commited we should add an step in the deployment that runs the compilation (we could do that if you want).
Yes, let me make a script for this.
Saw that you are using the version 2.0.0-rc2 of the compiler. Can you upgrade to latest?
It is Compiler v2.0.1 I think. I will update it to 2.0.2.
Also, for programs it works awesome. But with contracts it tries anyways to run the main entrypoint. Can you change that? Basically changing the compiler for contracts, and not running any entrypoint, just check if it compiles.
Surely we can! It already has the function for this proposal. And all we need is just sth. like "Compiled success." or "Compiled failed." in the result dialog?
BTW: Can you tell me how to set up github pages for hugo.yml? I set my fork repo like this but .css and .js files are not there.
https://cryptonerdcn.github.io/cairo-by-example/index.html
Surely we can! It already has the function for this proposal. And all we need is just sth. like "Compiled success." or "Compiled failed." in the result dialog?
Yes! That would be amazing.
BTW: Can you tell me how to set up github pages for hugo.yml? I set my fork repo like this but .css and .js files are not there.
I'm hooking you up with someone that can answer this. He should be answering soon.
BTW: Can you tell me how to set up github pages for hugo.yml? I set my fork repo like this but .css and .js files are not there. https://cryptonerdcn.github.io/cairo-by-example/index.html
Hey there!
Thinking about what could be going wrong, I see that the extra stuff I see in your fork is the assets/ directory. Does this work out of the box with hugo build/serve when testing locally? Maybe we need to modify the hugo.yml to correctly deploy this new code/directory to GitHub Pages. Maybe this doesn't end up in public/, that is what's uploaded to GitHub for the deploy. This is just my gut feeling, I can run some tests and get back to you, as it could be an entirely different issue, but let's see.
Hey there! Thinking about what could be going wrong, I see that the extra stuff I see in your fork is the
assets/directory. Does this work out of the box with hugo build/serve when testing locally? Maybe we need to modify the hugo.yml to correctly deploy this new code/directory to GitHub Pages. Maybe this doesn't end up inpublic/, that is what's uploaded to GitHub for the deploy. This is just my gut feeling, I can run some tests and get back to you, as it could be an entirely different issue, but let's see.
Thanks for the reply @klaus993 ! In the local machine, it works perfectly.
In the Upload artifact step of my repo's github action, it seems everything was uploaded.
https://github.com/cryptonerdcn/cairo-by-example/actions/runs/5587110247/jobs/10212023055