@blazen-dev/wasi 0.5.4 → 0.6.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.
Files changed (2) hide show
  1. package/README.md +2 -2
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -16,7 +16,7 @@ The wasm sidecar (`@blazen-dev/blazen-wasm32-wasi`) is pulled in automatically a
16
16
 
17
17
  ```js
18
18
  import {
19
- CompletionModel,
19
+ Model,
20
20
  EmbeddingModel,
21
21
  AnthropicProvider,
22
22
  Workflow,
@@ -42,7 +42,7 @@ pnpm add blazen @blazen-dev/blazen-wasm32-wasi
42
42
  ```
43
43
 
44
44
  ```js
45
- import { CompletionModel } from 'blazen/workers';
45
+ import { Model } from 'blazen/workers';
46
46
  ```
47
47
 
48
48
  Both installs are required because the wasm sidecar is an optional peer-dependency on `blazen`. The `blazen/workers` subpath uses the same wrangler-static `import wasm from '@blazen-dev/blazen-wasm32-wasi/blazen.wasm32-wasi.wasm'` loader under the hood as this alias.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@blazen-dev/wasi",
3
- "version": "0.5.4",
3
+ "version": "0.6.0",
4
4
  "description": "Single-install Blazen package for Cloudflare Workers, Deno, and any WASI host. Re-exports @blazen-dev/blazen-wasm32-wasi and lists the wasm sidecar as a regular dependency, so `pnpm add @blazen-dev/wasi` is all that's needed. The umbrella `blazen` package targets Node servers and keeps the wasm sidecar out of the default install footprint.",
5
5
  "license": "MPL-2.0",
6
6
  "type": "module",
@@ -13,7 +13,7 @@
13
13
  "index.d.ts"
14
14
  ],
15
15
  "dependencies": {
16
- "@blazen-dev/blazen-wasm32-wasi": "0.5.4"
16
+ "@blazen-dev/blazen-wasm32-wasi": "0.6.0"
17
17
  },
18
18
  "publishConfig": {
19
19
  "access": "public"