Repository navigation
Improve JavaScript SDK readability and add bridge benchmarks - #104
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The JavaScript SDK and bridge were difficult to read, and the SDK README lacked complete usage examples. This makes the public JavaScript/TypeScript API, shared facade, Rust adapter, and Node worker easier to follow while preserving their behavior and public APIs.
Changes
0.1.0, preserving third-party versions.Validation
On updated
main, using macOS arm64, Node 24.13.1, and Rust 1.98.1:embed,nodefeatures: context isolation, cancellation, mutation refusal, watchdog/process cleanup, IPC framing, npm/native-addon compatibility, and storage recovery after restart.Performance evidence and limits
The included campaign was measured at the explicitly recorded earlier source revision, before the version/readability changes; it is not a new measurement of this PR head. On the shared development machine, median 32-client 1 KiB echo throughput was 14,154 req/s for V8 and 11,088 for Node; sharded durable writes were 459 and 451 TPS. All 41,344 acknowledged increments, including warmup, reconciled after cold recovery.
The report preserves hot-cell conflicts and the V8 64 KiB/32-client failures, including one confirmed execution-budget failure and another dispatch failure whose cause was not established. This PR does not fix those runtime limitations. Results use a local SQLite development bucket and closed-loop traffic; they do not establish production fleet capacity.