-
Notifications
You must be signed in to change notification settings - Fork 576
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
chore: upgrade wasmbuild to 0.6 #2362
Conversation
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.
Oh, this is hugely simplified. Nice!
LGTM
|
||
### CI | ||
|
||
If CI fails in `Verify Wasm hasn't changed` step, you need to download built |
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.
Does this mean there is no diffs anymore in the built wasm based on the platforms?
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.
Yeah there’s no diffs. If the inputs are the same then the CI will pass. If someone builds on Windows then the output will be slightly different than if someone build on Linux, but the output should be functionally the same. So if the CI fails they should only have to run the deno task regardless of their OS, then recommit and it should pass the CI.
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.
Thanks for the clarification! Makes sense
--js-ext mjs
flag to output anmjs
extension--check
flag for verifying the output is up to date (works across operating systems)