-
Notifications
You must be signed in to change notification settings - Fork 251
Issues: bytecodealliance/wasm-tools
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[wasmparser] 0.218.0 test suite fails with
use of undeclared crate or module
wat`
#1947
opened Dec 10, 2024 by
Apteryks
[wasm-metadata] support displaying SBOM data embedded in components
#1924
opened Nov 29, 2024 by
yoshuawuyts
wit: unexpected error when referencing the package itself in exports
#1809
opened Sep 19, 2024 by
Mossaka
wit: propose to propogate World's name to inline Interfaces' names
#1805
opened Sep 19, 2024 by
Mossaka
shrink: Ineffective on non-tree-like expressions (?)
wasm-mutate
Issues related to the `wasm-mutate` crate
#1633
opened Jun 24, 2024 by
alexcrichton
wasi-virt throws error in wasm-compose (redirected from wasi-virt to Wasm-tools)
wasm-compose
Issues related to the `wasm-compose` crate
#1565
opened May 17, 2024 by
thesuhas
proposal: wit-parser: create distinct imported and exported TypeDefs, Functions, and Interfaces in a Resolve
#1497
opened Apr 15, 2024 by
ydnar
wasmparser::validator::ComponentState::validate_and_register_named_types
should return Result
instead of bool
#1486
opened Apr 4, 2024 by
rylev
Add a top-down code generation option to Related to the wasm-smith crate and creating wasm modules for fuzzing
wasm-smith
wasm-smith
#1484
opened Apr 3, 2024 by
fitzgen
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-11-27.