[WIP] Include current wit-bindgen configuration #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bindings for JS/TS are currently auto-generated by an earlier version of
wit-bindgen
, the result of which is included in this repo attypescript/src/bindings
. This PR serves as both documentation and initial reproduction of the process for generating these bindings from awit
file.The
wit
interface is derived from @ospencer's original PR, removing the APIs that have been deprecated since.Note that generating the JS bindings uses an older, specific version of
wit-bindgen
and JS binding generation has been removed in later versions, this PR andwit
interface could serve as a basis of bringing this feature up-to-date with the WebAssembly Component Model and modern versions ofwit-bindgen
.Please also note, that albeit the Dockerfile will generate the Rust bindings, as provided by this version of wit-bindgen, the current SDK uses manually written Rust language bindings, not auto-generated ones.