You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The easiest way to get started is by using one of these wrapper libraries that
39
39
already have all of the WASM host imports resolved.
40
40
41
-
For JavaScript users, you can use npm, [pnpm], [Yarn], or your other favorite npm package manager to install
42
-
[`hello-world-rust-wasm-component`] from npm.
41
+
For JavaScript users, you can use npm, [pnpm], [Yarn], or your other favorite
42
+
npm package manager to install [`hello-world-rust-wasm-component`] from npm.
43
43
44
44
```sh
45
45
npm install hello-world-rust-wasm-component
46
46
```
47
47
48
-
If you prefer to customize the Javascript ↔ WASM component bindings, you can use
49
-
[bytecodealliance/jco] to generate your own bindings.
48
+
If you prefer to customize the Javascript ↔ WASM component bindings, you can
49
+
use [bytecodealliance/jco] to generate your own bindings.
50
50
51
51
<!-- For Python users, you can use pip, [Poetry], or another PyPI package manager to
52
52
install [`hello-world-rust-wasm-component`] from PyPI.
@@ -82,9 +82,21 @@ For language-specific binding documentation, check out
82
82
./build.sh --release
83
83
```
84
84
85
-
ℹ You'll need [`wasm-tools`] installed which you can get via `cargo install wasm-tools`.
85
+
ℹ You'll need [`wasm-tools`] installed which you can get via
86
+
`cargo install wasm-tools`.
86
87
87
-
The `wasi_snapshot_preview1.reactor.wasm` is the adapter module to shim the component API over top of the existing WASI API. Keep it updated from [bytecodealliance/wasmtime releases]. Since this is a library we want the "reactor" version.
88
+
The `wasi_snapshot_preview1.reactor.wasm` is the adapter module to shim the
89
+
component API over top of the existing WASI API. Keep it updated from
90
+
[bytecodealliance/wasmtime releases]. Since this is a library we want the
91
+
"reactor" version.
92
+
93
+
🚚 To create a new release, don't use the GitHub UI directly; use the [draft
94
+
release] GitHub Actions workflow to create the initial draft release with the
95
+
compiled WASM artifact. Then you can edit that release and publish it as normal.
96
+
Make sure the `version` field is correct in `Cargo.toml` before drafting the
97
+
release; it's used to choose the `v${version}` tag name for the release. Also
98
+
try not to change the artifacts attached to the draft release; they were
0 commit comments