Skip to content

chore: require Node 22 LTS and drop the WASIp2 fallback - #122

Merged
harlan-zw merged 1 commit into
mainfrom
chore/drop-node18-and-wasi-fallback
Aug 21, 2026
Merged

chore: require Node 22 LTS and drop the WASIp2 fallback#122
harlan-zw merged 1 commit into
mainfrom
chore/drop-node18-and-wasi-fallback

Conversation

@harlan-zw

Copy link
Copy Markdown
Collaborator

Why

The v3 native rewrite left two loose ends: engines still allowed Node 18 while CI and the other packages already require Node 22 LTS, and the WASIp2 fallback never shipped.

Changes

  • engines: >=18.18.0 / >=18 -> >=22.0.0 in skilld and skilld-protocol (matches skilld-harness)
  • remove ws from skilld-harness and the catalog (never imported; Node 22 has native WebSocket)
  • remove the unpublished WASIp2 fallback:
    • packages/cli-wasm32-wasi and @bytecodealliance/preview2-shim catalog entry
    • crates/skilld-wasi, wit-bindgen workspace dep, wit/skilld-host.wit
    • scripts/v3-rust/build-component.sh, scripts/v3-rust/test-parity.sh, tests/fixtures/v3-rust/wasip2-no-go.json

Verification

  • pnpm install (lockfile updated)
  • cargo check --workspace and cargo clippy --workspace --all-targets -- -D warnings clean
  • pnpm test:js: 30/30 pass
  • tsc --noEmit in protocol + harness

Agent-generated.

- raise engines to >=22.0.0 in skilld and skilld-protocol
- remove the unused ws dependency from skilld-harness
- remove the unpublished WASIp2 fallback: skilld-cli-wasm32-wasi,
skilld-wasi crate, wit-bindgen, host WIT file, and its parity scripts
@harlan-zw
harlan-zw merged commit 9993a1f into mainAug 21, 2026
2 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@harlan-zw