Add Node and Bun support to the TypeScript client

[just-be-dev]

So, I've wanted to use this project outside of the deno ecosystem for a bit and it's high time to land a change to support both node and bun. Honestly, there's not really much of a dependency on deno to begin with. From a runtime perspective it's nice to have URL dependencies in a webview script but it's certainly not required. I'm not using FFI in this project at all given the binary approach (which I'm generally happy with). So, yeah. I still need to do the manual publishing of the package to NPM and setup the OIDC publishing step.

AI Summary

Reworks the Deno client into a cross-runtime TypeScript client that works on Node (>= 20.9), Deno, and Bun, published to both JSR (@justbe/webview, unchanged) and npm (@just-be/webview, new). Existing Deno/JSR consumers are unaffected — same package name, version, exports, and permission behavior.

Client changes (src/clients/deno/ → src/clients/typescript/)

• main.ts uses node: builtins everywhere (child_process, fs/promises, path, events), which all three runtimes support natively. Web streams became Node streams, with a persistent streaming TextDecoder (also fixes a latent bug where multi-byte UTF-8 chars split across chunks would corrupt).
• New runtime.ts holds the only runtime-conditional code: getEnv() preserves Deno's permission-guard behavior (no prompt without --allow-env), plus platformOs()/platformArch() normalizers.
• New logger.ts replaces @bcheidemann/tracing + @instrument() decorators — that dep is JSR-only (npm packages can't depend on JSR-scoped packages), and TC39 decorators can't run on Node from raw TS. Same LOG_LEVEL env contract; per-method span traces are gone.
• Public API is unchanged.

Packaging & CI

• New package.json / tsdown build / tsconfig.npm.json for the npm artifact (ESM + d.ts). The tsconfig is deliberately not named tsconfig.json — Deno 2.4 picks that up and it breaks deno check.
• deno.json sets nodeModulesDir: "none" so Deno and npm don't fight over node_modules.
• publish-deno.yml → publish-typescript-jsr.yml (logic unchanged, incl. deno-v* tags); new publish-typescript-npm.yml mirrors the version-gated pattern and publishes with --provenance.
• mise: :deno tasks renamed to :ts; new example:node, example:bun, verify-publish:npm, lint:ts-npm tasks; node + bun added to tools.
• Codegen now emits import { z } from "zod" (bare specifier); sync-versions.ts keeps package.json version locked to deno.json.

Verification

• Deno: deno lint, deno check, deno publish --dry-run, live smoke test (spawn → setTitle/getTitle round-trip → dispose) ✅
• Node: tsc typecheck, tsdown build, live smoke via tsx, tarball installed in a scratch project with zero registry config ✅
• Bun: live smoke test ✅
• mise run lint, npm pack contents, codegen idempotency ✅

Before npm publishing works

1. Add an NPM_TOKEN repo secret with publish rights to the @just-be scope.
2. The first @just-be/webview publish may need to be done manually to claim the name.

🤖 Generated with Claude Code