@blazen-dev/wasi 0.5.1 → 0.5.2

package/README.md

@@ -1,30 +1,51 @@
 # @blazen-dev/wasi
 
-Thin re-export alias for [`@blazen-dev/blazen-wasm32-wasi`](https://www.npmjs.com/package/@blazen-dev/blazen-wasm32-wasi) — the WASI build of the Blazen Node binding. Use it in Cloudflare Workers, Deno, or any other WASI host where you'd rather pin the WASI sidecar explicitly than rely on the umbrella `blazen` package's automatic platform resolution.
+The single-install Blazen package for Cloudflare Workers, Deno, and any other WASI host. Re-exports [`@blazen-dev/blazen-wasm32-wasi`](https://www.npmjs.com/package/@blazen-dev/blazen-wasm32-wasi) — the napi-rs WASI build of Blazen — and lists the wasm sidecar as a regular dependency so `pnpm add @blazen-dev/wasi` is all you need.
 
-## Recommended path
-
-Just install the umbrella package and let it resolve the right sidecar for your host:
+## Install
 
 ```bash
-npm install blazen
+pnpm add @blazen-dev/wasi
+# or
+npm install @blazen-dev/wasi
 ```
 
-The `blazen` umbrella package already pulls in `@blazen-dev/blazen-wasm32-wasi` automatically when no native binary matches the host (e.g. Cloudflare Workers, Deno, WASI runtimes). You do **not** need this alias for that case.
+The wasm sidecar (`@blazen-dev/blazen-wasm32-wasi`) is pulled in automatically as a transitive dependency. No second install, no Vite/Rollup workaround plugins, no `ssr.external` lists, no `manualChunks`. Works out of the box with wrangler ≥ 3.15 and `@cloudflare/vite-plugin`.
+
+## Usage
+
+```js
+import {
+  CompletionModel,
+  EmbeddingModel,
+  AnthropicProvider,
+  Workflow,
+} from '@blazen-dev/wasi';
+```
 
-## When to use this alias
+The export surface is identical to the main `blazen` package; only the binding implementation differs (wasm32-wasi build instead of a per-platform `.node` binary).
 
-Install `@blazen-dev/wasi` only when you want an explicit pin on the WASI build — e.g. you're authoring a library that must run on Workers and you want the dep graph to declare that intent unambiguously, or you want to skip umbrella resolution entirely.
+## When to use this instead of `blazen`
+
+The umbrella `blazen` package targets Node servers and installs a per-platform native `.node` binary. The wasm sidecar is an *optional* peer-dependency there, intentionally kept out of Node-only install footprints. Use this package when:
+
+- You're deploying to Cloudflare Workers, Deno Deploy, Fastly Compute, or another WASI host where the native `.node` binary won't load.
+- You want a single `pnpm add` line that pulls everything needed for the target runtime.
+- You want the dependency graph to clearly declare your Workers/edge intent.
+
+## Alternative: `blazen/workers` subpath
+
+If you'd rather list `blazen` in your dependency tree (mirroring a Node deployment) and explicitly pin the wasm sidecar yourself:
 
 ```bash
-npm install @blazen-dev/wasi
+pnpm add blazen @blazen-dev/blazen-wasm32-wasi
 ```
 
 ```js
-import { /* your APIs */ } from '@blazen-dev/wasi';
+import { CompletionModel } from 'blazen/workers';
 ```
 
-The exports are identical to `@blazen-dev/blazen-wasm32-wasi`; this package only re-exports.
+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.
 
 ## Documentation
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@blazen-dev/wasi",
-  "version": "0.5.1",
-  "description": "Blazen wasi build of the Node binding — thin re-export of @blazen-dev/blazen-wasm32-wasi for explicit installs in Cloudflare Workers / Deno / any WASI host. The umbrella `blazen` package auto-resolves the wasi sidecar without this alias; install this only if you want an explicit pin.",
+  "version": "0.5.2",
+  "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.",
   "license": "MPL-2.0",
   "type": "module",
   "main": "index.cjs",
@@ -13,7 +13,7 @@
     "index.d.ts"
   ],
   "dependencies": {
-    "@blazen-dev/blazen-wasm32-wasi": "0.5.1"
+    "@blazen-dev/blazen-wasm32-wasi": "0.5.2"
   },
   "publishConfig": {
     "access": "public"