-
Notifications
You must be signed in to change notification settings - Fork 7
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
Use Wasm to hash dep components, rather than tar
#25
Comments
tar
tar
I think the part I would tackle first is just enhancing Then we can start using this to publish interface packages (as binaries) to GitHub artifacts and eventually a registry. Once we start having binaries for packages built using CI/CD available somewhere, it makes sense to then add the ability to take those as an input for dependencies. |
i.e. #24 |
Ah, missed the |
Refs #24
Instead of
tar
-packing the dependencies to compute the digest, use https://github.com/bytecodealliance/wasm-tools to assemble a Wasm containing all the interfaces and worlds within the fetched package and hash that.For a given dependency
X
, producedeps/X.wasm
alongsidedeps/X
directory for backwards compatibility at least until the released version of https://github.com/bytecodealliance/wit-bindgen can take Wasm as inputThe text was updated successfully, but these errors were encountered: