Dispose args when a WritableStream stub call fails by ndisidore · Pull Request #243 · cloudflare/capnweb

ndisidore · 2026-08-12T20:48:25Z

WritableStreamStubHook.call() disposed its copied arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid. those throws returned an ErrorStubHook with the owned arguments stranded. This moves the disposal into the catch so every failure path releases them, matching ReadableStreamStubHook.

Found while working on the failure-path disposal fixes in #241, but independent of them so it's split out here.

WritableStreamStubHook.call() disposed its arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid -- those throws returned an ErrorStubHook with the owned arguments stranded. Move the disposal to the catch so every failure path releases them, matching ReadableStreamStubHook.

changeset-bot · 2026-08-12T20:48:29Z

🦋 Changeset detected

Latest commit: 3a9b1bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
capnweb	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2026-08-12T20:49:04Z

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@243

commit: 3a9b1bc

ask-bonk · 2026-08-12T20:49:39Z

All imports are valid exports. The change is minimal, correct, and well-covered:

The disposal is correctly moved into the catch block, so all three synchronous failure paths (disposed hook, invalid path shape, unknown method) release the owned args.
No double-dispose risk: deliverStreamWrite/deliverCall are async, so they never throw synchronously into the catch; and RpcPayload.dispose() is idempotent anyway.
Behavior now matches ReadableStreamStubHook.call().
Tests cover both new failure paths; a changeset is included.

LGTM

github run

0.12.0 added a way to construct an `RpcPromise` from an ordinary `Promise`, so callers can pipeline against a capability you have not obtained yet. That is new public API, not a bug fix, and the docs said nothing about it -- main documented it in the root README, which this branch replaced with a pointer to here, so the merge would otherwise have dropped it on the floor. `concepts/promises.md` gets a section, and it leans on the equivalence the API docs make: wrapping a promise means the same thing as a local-loopback call returning it. That is worth stating plainly, because it derives all the rules that would otherwise have to be listed as a second set to memorise -- the resolution is serialized, targets and functions come back as stubs, ownership transfers, rejections propagate. The ownership one is the sharp edge and is called out: disposing the promise disposes the resolution, so resolve with a `.dup()` if you want to keep a stub. The cheat sheet gets a one-line constructor note, matching the one `RpcStub` already has. Also: a Changelog entry in the sidebar under Reference, pointing at the GitHub releases page. Off-site on purpose -- release notes are generated from changesets on every publish, so a page here would be a copy that goes stale the next time anyone ships. Nimbus recognises the absolute URL and adds `target="_blank" rel="noopener"` itself. Nothing else in the merge needed documenting. #241, #243, #251 and #253 are leak and typing fixes with no API surface to describe; #253's note that `RpcPromise<RpcStub<T>>` should now be written `RpcPromise<T>` applies to no annotation anywhere in these pages.

ndisidore · 2026-08-12T20:48:25Z

WritableStreamStubHook.call() disposed its copied arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid. those throws returned an ErrorStubHook with the owned arguments stranded. This moves the disposal into the catch so every failure path releases them, matching ReadableStreamStubHook.

Found while working on the failure-path disposal fixes in #241, but independent of them so it's split out here.

WritableStreamStubHook.call() disposed its arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid -- those throws returned an ErrorStubHook with the owned arguments stranded. Move the disposal to the catch so every failure path releases them, matching ReadableStreamStubHook.

changeset-bot · 2026-08-12T20:48:29Z

🦋 Changeset detected

Latest commit: 3a9b1bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
capnweb	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2026-08-12T20:49:04Z

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@243

commit: 3a9b1bc

ask-bonk · 2026-08-12T20:49:39Z

All imports are valid exports. The change is minimal, correct, and well-covered:

The disposal is correctly moved into the catch block, so all three synchronous failure paths (disposed hook, invalid path shape, unknown method) release the owned args.
No double-dispose risk: deliverStreamWrite/deliverCall are async, so they never throw synchronously into the catch; and RpcPayload.dispose() is idempotent anyway.
Behavior now matches ReadableStreamStubHook.call().
Tests cover both new failure paths; a changeset is included.

LGTM

github run

0.12.0 added a way to construct an `RpcPromise` from an ordinary `Promise`, so callers can pipeline against a capability you have not obtained yet. That is new public API, not a bug fix, and the docs said nothing about it -- main documented it in the root README, which this branch replaced with a pointer to here, so the merge would otherwise have dropped it on the floor. `concepts/promises.md` gets a section, and it leans on the equivalence the API docs make: wrapping a promise means the same thing as a local-loopback call returning it. That is worth stating plainly, because it derives all the rules that would otherwise have to be listed as a second set to memorise -- the resolution is serialized, targets and functions come back as stubs, ownership transfers, rejections propagate. The ownership one is the sharp edge and is called out: disposing the promise disposes the resolution, so resolve with a `.dup()` if you want to keep a stub. The cheat sheet gets a one-line constructor note, matching the one `RpcStub` already has. Also: a Changelog entry in the sidebar under Reference, pointing at the GitHub releases page. Off-site on purpose -- release notes are generated from changesets on every publish, so a page here would be a copy that goes stale the next time anyone ships. Nimbus recognises the absolute URL and adds `target="_blank" rel="noopener"` itself. Nothing else in the merge needed documenting. #241, #243, #251 and #253 are leak and typing fixes with no API surface to describe; #253's note that `RpcPromise<RpcStub<T>>` should now be written `RpcPromise<T>` applies to no annotation anywhere in these pages.

ndisidore · 2026-08-12T20:48:25Z

WritableStreamStubHook.call() disposed its copied arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid. those throws returned an ErrorStubHook with the owned arguments stranded. This moves the disposal into the catch so every failure path releases them, matching ReadableStreamStubHook.

Found while working on the failure-path disposal fixes in #241, but independent of them so it's split out here.

WritableStreamStubHook.call() disposed its arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid -- those throws returned an ErrorStubHook with the owned arguments stranded. Move the disposal to the catch so every failure path releases them, matching ReadableStreamStubHook.

changeset-bot · 2026-08-12T20:48:29Z

🦋 Changeset detected

Latest commit: 3a9b1bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
capnweb	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2026-08-12T20:49:04Z

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@243

commit: 3a9b1bc

ask-bonk · 2026-08-12T20:49:39Z

All imports are valid exports. The change is minimal, correct, and well-covered:

The disposal is correctly moved into the catch block, so all three synchronous failure paths (disposed hook, invalid path shape, unknown method) release the owned args.
No double-dispose risk: deliverStreamWrite/deliverCall are async, so they never throw synchronously into the catch; and RpcPayload.dispose() is idempotent anyway.
Behavior now matches ReadableStreamStubHook.call().
Tests cover both new failure paths; a changeset is included.

LGTM

github run

0.12.0 added a way to construct an `RpcPromise` from an ordinary `Promise`, so callers can pipeline against a capability you have not obtained yet. That is new public API, not a bug fix, and the docs said nothing about it -- main documented it in the root README, which this branch replaced with a pointer to here, so the merge would otherwise have dropped it on the floor. `concepts/promises.md` gets a section, and it leans on the equivalence the API docs make: wrapping a promise means the same thing as a local-loopback call returning it. That is worth stating plainly, because it derives all the rules that would otherwise have to be listed as a second set to memorise -- the resolution is serialized, targets and functions come back as stubs, ownership transfers, rejections propagate. The ownership one is the sharp edge and is called out: disposing the promise disposes the resolution, so resolve with a `.dup()` if you want to keep a stub. The cheat sheet gets a one-line constructor note, matching the one `RpcStub` already has. Also: a Changelog entry in the sidebar under Reference, pointing at the GitHub releases page. Off-site on purpose -- release notes are generated from changesets on every publish, so a page here would be a copy that goes stale the next time anyone ships. Nimbus recognises the absolute URL and adds `target="_blank" rel="noopener"` itself. Nothing else in the merge needed documenting. #241, #243, #251 and #253 are leak and typing fixes with no API surface to describe; #253's note that `RpcPromise<RpcStub<T>>` should now be written `RpcPromise<T>` applies to no annotation anywhere in these pages.

ndisidore · 2026-08-12T20:48:25Z

WritableStreamStubHook.call() disposed its copied arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid. those throws returned an ErrorStubHook with the owned arguments stranded. This moves the disposal into the catch so every failure path releases them, matching ReadableStreamStubHook.

Found while working on the failure-path disposal fixes in #241, but independent of them so it's split out here.

WritableStreamStubHook.call() disposed its arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid -- those throws returned an ErrorStubHook with the owned arguments stranded. Move the disposal to the catch so every failure path releases them, matching ReadableStreamStubHook.

changeset-bot · 2026-08-12T20:48:29Z

🦋 Changeset detected

Latest commit: 3a9b1bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
capnweb	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2026-08-12T20:49:04Z

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@243

commit: 3a9b1bc

ask-bonk · 2026-08-12T20:49:39Z

All imports are valid exports. The change is minimal, correct, and well-covered:

The disposal is correctly moved into the catch block, so all three synchronous failure paths (disposed hook, invalid path shape, unknown method) release the owned args.
No double-dispose risk: deliverStreamWrite/deliverCall are async, so they never throw synchronously into the catch; and RpcPayload.dispose() is idempotent anyway.
Behavior now matches ReadableStreamStubHook.call().
Tests cover both new failure paths; a changeset is included.

LGTM

github run

0.12.0 added a way to construct an `RpcPromise` from an ordinary `Promise`, so callers can pipeline against a capability you have not obtained yet. That is new public API, not a bug fix, and the docs said nothing about it -- main documented it in the root README, which this branch replaced with a pointer to here, so the merge would otherwise have dropped it on the floor. `concepts/promises.md` gets a section, and it leans on the equivalence the API docs make: wrapping a promise means the same thing as a local-loopback call returning it. That is worth stating plainly, because it derives all the rules that would otherwise have to be listed as a second set to memorise -- the resolution is serialized, targets and functions come back as stubs, ownership transfers, rejections propagate. The ownership one is the sharp edge and is called out: disposing the promise disposes the resolution, so resolve with a `.dup()` if you want to keep a stub. The cheat sheet gets a one-line constructor note, matching the one `RpcStub` already has. Also: a Changelog entry in the sidebar under Reference, pointing at the GitHub releases page. Off-site on purpose -- release notes are generated from changesets on every publish, so a page here would be a copy that goes stale the next time anyone ships. Nimbus recognises the absolute URL and adds `target="_blank" rel="noopener"` itself. Nothing else in the merge needed documenting. #241, #243, #251 and #253 are leak and typing fixes with no API surface to describe; #253's note that `RpcPromise<RpcStub<T>>` should now be written `RpcPromise<T>` applies to no annotation anywhere in these pages.

ndisidore · 2026-08-12T20:48:25Z

WritableStreamStubHook.call() disposed its copied arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid. those throws returned an ErrorStubHook with the owned arguments stranded. This moves the disposal into the catch so every failure path releases them, matching ReadableStreamStubHook.

Found while working on the failure-path disposal fixes in #241, but independent of them so it's split out here.

WritableStreamStubHook.call() disposed its arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid -- those throws returned an ErrorStubHook with the owned arguments stranded. Move the disposal to the catch so every failure path releases them, matching ReadableStreamStubHook.

changeset-bot · 2026-08-12T20:48:29Z

🦋 Changeset detected

Latest commit: 3a9b1bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
capnweb	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2026-08-12T20:49:04Z

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@243

commit: 3a9b1bc

ask-bonk · 2026-08-12T20:49:39Z

All imports are valid exports. The change is minimal, correct, and well-covered:

The disposal is correctly moved into the catch block, so all three synchronous failure paths (disposed hook, invalid path shape, unknown method) release the owned args.
No double-dispose risk: deliverStreamWrite/deliverCall are async, so they never throw synchronously into the catch; and RpcPayload.dispose() is idempotent anyway.
Behavior now matches ReadableStreamStubHook.call().
Tests cover both new failure paths; a changeset is included.

LGTM

github run

0.12.0 added a way to construct an `RpcPromise` from an ordinary `Promise`, so callers can pipeline against a capability you have not obtained yet. That is new public API, not a bug fix, and the docs said nothing about it -- main documented it in the root README, which this branch replaced with a pointer to here, so the merge would otherwise have dropped it on the floor. `concepts/promises.md` gets a section, and it leans on the equivalence the API docs make: wrapping a promise means the same thing as a local-loopback call returning it. That is worth stating plainly, because it derives all the rules that would otherwise have to be listed as a second set to memorise -- the resolution is serialized, targets and functions come back as stubs, ownership transfers, rejections propagate. The ownership one is the sharp edge and is called out: disposing the promise disposes the resolution, so resolve with a `.dup()` if you want to keep a stub. The cheat sheet gets a one-line constructor note, matching the one `RpcStub` already has. Also: a Changelog entry in the sidebar under Reference, pointing at the GitHub releases page. Off-site on purpose -- release notes are generated from changesets on every publish, so a page here would be a copy that goes stale the next time anyone ships. Nimbus recognises the absolute URL and adds `target="_blank" rel="noopener"` itself. Nothing else in the merge needed documenting. #241, #243, #251 and #253 are leak and typing fixes with no API surface to describe; #253's note that `RpcPromise<RpcStub<T>>` should now be written `RpcPromise<T>` applies to no annotation anywhere in these pages.

ndisidore · 2026-08-12T20:48:25Z

WritableStreamStubHook.call() disposed its copied arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid. those throws returned an ErrorStubHook with the owned arguments stranded. This moves the disposal into the catch so every failure path releases them, matching ReadableStreamStubHook.

Found while working on the failure-path disposal fixes in #241, but independent of them so it's split out here.

WritableStreamStubHook.call() disposed its arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid -- those throws returned an ErrorStubHook with the owned arguments stranded. Move the disposal to the catch so every failure path releases them, matching ReadableStreamStubHook.

changeset-bot · 2026-08-12T20:48:29Z

🦋 Changeset detected

Latest commit: 3a9b1bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
capnweb	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2026-08-12T20:49:04Z

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@243

commit: 3a9b1bc

ask-bonk · 2026-08-12T20:49:39Z

All imports are valid exports. The change is minimal, correct, and well-covered:

The disposal is correctly moved into the catch block, so all three synchronous failure paths (disposed hook, invalid path shape, unknown method) release the owned args.
No double-dispose risk: deliverStreamWrite/deliverCall are async, so they never throw synchronously into the catch; and RpcPayload.dispose() is idempotent anyway.
Behavior now matches ReadableStreamStubHook.call().
Tests cover both new failure paths; a changeset is included.

LGTM

github run

0.12.0 added a way to construct an `RpcPromise` from an ordinary `Promise`, so callers can pipeline against a capability you have not obtained yet. That is new public API, not a bug fix, and the docs said nothing about it -- main documented it in the root README, which this branch replaced with a pointer to here, so the merge would otherwise have dropped it on the floor. `concepts/promises.md` gets a section, and it leans on the equivalence the API docs make: wrapping a promise means the same thing as a local-loopback call returning it. That is worth stating plainly, because it derives all the rules that would otherwise have to be listed as a second set to memorise -- the resolution is serialized, targets and functions come back as stubs, ownership transfers, rejections propagate. The ownership one is the sharp edge and is called out: disposing the promise disposes the resolution, so resolve with a `.dup()` if you want to keep a stub. The cheat sheet gets a one-line constructor note, matching the one `RpcStub` already has. Also: a Changelog entry in the sidebar under Reference, pointing at the GitHub releases page. Off-site on purpose -- release notes are generated from changesets on every publish, so a page here would be a copy that goes stale the next time anyone ships. Nimbus recognises the absolute URL and adds `target="_blank" rel="noopener"` itself. Nothing else in the merge needed documenting. #241, #243, #251 and #253 are leak and typing fixes with no API surface to describe; #253's note that `RpcPromise<RpcStub<T>>` should now be written `RpcPromise<T>` applies to no annotation anywhere in these pages.

ndisidore · 2026-08-12T20:48:25Z

WritableStreamStubHook.call() disposed its copied arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid. those throws returned an ErrorStubHook with the owned arguments stranded. This moves the disposal into the catch so every failure path releases them, matching ReadableStreamStubHook.

Found while working on the failure-path disposal fixes in #241, but independent of them so it's split out here.

WritableStreamStubHook.call() disposed its arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid -- those throws returned an ErrorStubHook with the owned arguments stranded. Move the disposal to the catch so every failure path releases them, matching ReadableStreamStubHook.

changeset-bot · 2026-08-12T20:48:29Z

🦋 Changeset detected

Latest commit: 3a9b1bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
capnweb	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2026-08-12T20:49:04Z

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@243

commit: 3a9b1bc

ask-bonk · 2026-08-12T20:49:39Z

All imports are valid exports. The change is minimal, correct, and well-covered:

The disposal is correctly moved into the catch block, so all three synchronous failure paths (disposed hook, invalid path shape, unknown method) release the owned args.
No double-dispose risk: deliverStreamWrite/deliverCall are async, so they never throw synchronously into the catch; and RpcPayload.dispose() is idempotent anyway.
Behavior now matches ReadableStreamStubHook.call().
Tests cover both new failure paths; a changeset is included.

LGTM

github run

0.12.0 added a way to construct an `RpcPromise` from an ordinary `Promise`, so callers can pipeline against a capability you have not obtained yet. That is new public API, not a bug fix, and the docs said nothing about it -- main documented it in the root README, which this branch replaced with a pointer to here, so the merge would otherwise have dropped it on the floor. `concepts/promises.md` gets a section, and it leans on the equivalence the API docs make: wrapping a promise means the same thing as a local-loopback call returning it. That is worth stating plainly, because it derives all the rules that would otherwise have to be listed as a second set to memorise -- the resolution is serialized, targets and functions come back as stubs, ownership transfers, rejections propagate. The ownership one is the sharp edge and is called out: disposing the promise disposes the resolution, so resolve with a `.dup()` if you want to keep a stub. The cheat sheet gets a one-line constructor note, matching the one `RpcStub` already has. Also: a Changelog entry in the sidebar under Reference, pointing at the GitHub releases page. Off-site on purpose -- release notes are generated from changesets on every publish, so a page here would be a copy that goes stale the next time anyone ships. Nimbus recognises the absolute URL and adds `target="_blank" rel="noopener"` itself. Nothing else in the merge needed documenting. #241, #243, #251 and #253 are leak and typing fixes with no API surface to describe; #253's note that `RpcPromise<RpcStub<T>>` should now be written `RpcPromise<T>` applies to no annotation anywhere in these pages.

ndisidore · 2026-08-12T20:48:25Z

WritableStreamStubHook.call() disposed its copied arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid. those throws returned an ErrorStubHook with the owned arguments stranded. This moves the disposal into the catch so every failure path releases them, matching ReadableStreamStubHook.

Found while working on the failure-path disposal fixes in #241, but independent of them so it's split out here.

WritableStreamStubHook.call() disposed its arguments on the unknown-method path but not when the hook was already disposed or the path shape was invalid -- those throws returned an ErrorStubHook with the owned arguments stranded. Move the disposal to the catch so every failure path releases them, matching ReadableStreamStubHook.

changeset-bot · 2026-08-12T20:48:29Z

🦋 Changeset detected

Latest commit: 3a9b1bc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
capnweb	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2026-08-12T20:49:04Z

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/capnweb@243

commit: 3a9b1bc

ask-bonk · 2026-08-12T20:49:39Z

All imports are valid exports. The change is minimal, correct, and well-covered:

The disposal is correctly moved into the catch block, so all three synchronous failure paths (disposed hook, invalid path shape, unknown method) release the owned args.
No double-dispose risk: deliverStreamWrite/deliverCall are async, so they never throw synchronously into the catch; and RpcPayload.dispose() is idempotent anyway.
Behavior now matches ReadableStreamStubHook.call().
Tests cover both new failure paths; a changeset is included.

LGTM

github run

0.12.0 added a way to construct an `RpcPromise` from an ordinary `Promise`, so callers can pipeline against a capability you have not obtained yet. That is new public API, not a bug fix, and the docs said nothing about it -- main documented it in the root README, which this branch replaced with a pointer to here, so the merge would otherwise have dropped it on the floor. `concepts/promises.md` gets a section, and it leans on the equivalence the API docs make: wrapping a promise means the same thing as a local-loopback call returning it. That is worth stating plainly, because it derives all the rules that would otherwise have to be listed as a second set to memorise -- the resolution is serialized, targets and functions come back as stubs, ownership transfers, rejections propagate. The ownership one is the sharp edge and is called out: disposing the promise disposes the resolution, so resolve with a `.dup()` if you want to keep a stub. The cheat sheet gets a one-line constructor note, matching the one `RpcStub` already has. Also: a Changelog entry in the sidebar under Reference, pointing at the GitHub releases page. Off-site on purpose -- release notes are generated from changesets on every publish, so a page here would be a copy that goes stale the next time anyone ships. Nimbus recognises the absolute URL and adds `target="_blank" rel="noopener"` itself. Nothing else in the merge needed documenting. #241, #243, #251 and #253 are leak and typing fixes with no API surface to describe; #253's note that `RpcPromise<RpcStub<T>>` should now be written `RpcPromise<T>` applies to no annotation anywhere in these pages.

ndisidore marked this pull request as ready for review August 12, 2026 22:15

kentonv approved these changes Aug 13, 2026
View reviewed changes

ndisidore merged commit 7e864a8 into mainAug 13, 2026
9 checks passed

github-actionsBot mentioned this pull request Aug 13, 2026
Version Packages #249
Merged

ask-bonkBot mentioned this pull request Aug 14, 2026
docs: documentation site, with the examples as embedded playgrounds #233
Merged