@ferrflow/wasm 5.40.0 → 5.42.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +21 -0
- package/ferrflow_wasm_bg.wasm +0 -0
- package/package.json +1 -1
package/README.md
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# ferrflow-wasm
|
|
2
|
+
|
|
3
|
+
FerrFlow's core functions compiled to WebAssembly, published to npm as
|
|
4
|
+
[`@ferrflow/wasm`](https://www.npmjs.com/package/@ferrflow/wasm) and consumed by
|
|
5
|
+
the ferrflow.com playground.
|
|
6
|
+
|
|
7
|
+
## Versioning
|
|
8
|
+
|
|
9
|
+
`ferrflow-wasm` is versioned in lockstep with the `ferrflow` crate — there is no
|
|
10
|
+
independent version line. The release pipeline is the single source of truth:
|
|
11
|
+
|
|
12
|
+
- `ferrflow-wasm/Cargo.toml` is listed in the `ferrflow` package's
|
|
13
|
+
`versionedFiles` (see [`.ferrflow`](../.ferrflow)), so every `ferrflow release`
|
|
14
|
+
writes the new version into it in the same commit as `Cargo.toml` and the npm
|
|
15
|
+
platform manifests.
|
|
16
|
+
- The npm publish (`npm/scripts/publish-wasm.sh`) stamps the package version from
|
|
17
|
+
the release git tag, so `@ferrflow/wasm@X.Y.Z` always matches `ferrflow@X.Y.Z`.
|
|
18
|
+
|
|
19
|
+
The playground therefore runs the same logic as the CLI at that version. When a
|
|
20
|
+
new major ships, bump the playground's `@ferrflow/wasm` dependency in
|
|
21
|
+
`FerrFlow-Cloud` to match.
|
package/ferrflow_wasm_bg.wasm
CHANGED
|
Binary file
|