poc(runtime): real node lib path/buffer/fs (sync+async) via internalBinding shims + wasm simdutf#1726
Conversation
Member
Author
…inding shims + wasm simdutf Stage 1: node v26 lib/path.js + lib/buffer.js load unmodified in the embedded V8 runtime via node's real realm.js loader and JS binding shims. Stage 2: lib/fs.js sync ops pass against an in-memory backend AND the real kernel/ChunkedVFS in a full sidecar VM via the _fs* sync bridge globals. Stage 2.5: buffer validation/length codecs backed by upstream simdutf compiled to wasm32-wasip1 with the patched sysroot, running in V8's own wasm engine. Stage 3: async fs end to end - FSReqCallback/kUsePromises adapter, real lib/timers.js wired to a POC scheduler (getTimerCallbacks/setupTimers), callback+promise APIs, node-exact completion ordering (sync,tick,micro,fs), and fs.createReadStream/createWriteStream/pipe over 1MB through the real internal/streams stack; bridge backend completes via _fs*Async events.
|
🚅 Deployed to the agentos-pr-1726 environment in agentos
|
NathanFlurry
force-pushed
the
stack/docs-internal-node-stdlib-replacement-spec-v3-review-hardened-user-decisions-wyqxqylo
branch
from
7915149 to
5b4b67f
Compare
NathanFlurry
force-pushed
the
stack/poc-runtime-real-node-lib-path-buffer-fs-sync-async-via-internalbinding-shims-wasm-simdutf-ulxrmvqv
branch
from
623f9f8 to
cdd38cb
Compare
This was referenced Jul 10, 2026
Closed
This was referenced Jul 10, 2026
Closed
Closed
Closed
NathanFlurry
deleted the branch
stack/docs-internal-node-stdlib-replacement-spec-v3-review-hardened-user-decisions-wyqxqylo
NathanFlurry
deleted the
stack/poc-runtime-real-node-lib-path-buffer-fs-sync-async-via-internalbinding-shims-wasm-simdutf-ulxrmvqv
branch
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
1 participant
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.
Stage 1: node v26 lib/path.js + lib/buffer.js load unmodified in the embedded
V8 runtime via node's real realm.js loader and JS binding shims.
Stage 2: lib/fs.js sync ops pass against an in-memory backend AND the real
kernel/ChunkedVFS in a full sidecar VM via the _fs* sync bridge globals.
Stage 2.5: buffer validation/length codecs backed by upstream simdutf compiled
to wasm32-wasip1 with the patched sysroot, running in V8's own wasm engine.
Stage 3: async fs end to end - FSReqCallback/kUsePromises adapter, real
lib/timers.js wired to a POC scheduler (getTimerCallbacks/setupTimers),
callback+promise APIs, node-exact completion ordering (sync,tick,micro,fs),
and fs.createReadStream/createWriteStream/pipe over 1MB through the real
internal/streams stack; bridge backend completes via _fs*Async events.