Skip to content

doc: clarify vfs is not a sandbox#64143

Open
mcollina wants to merge 1 commit into
nodejs:mainfrom
mcollina:doc-vfs-not-sandbox
Open

doc: clarify vfs is not a sandbox#64143
mcollina wants to merge 1 commit into
nodejs:mainfrom
mcollina:doc-vfs-not-sandbox

Conversation

@mcollina

@mcollina mcollina commented Jun 26, 2026

Copy link
Copy Markdown
Member

Clarify that node:vfs is not a sandbox, permission system, or security boundary.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/tsc

@mcollina mcollina requested a review from RafaelGSS June 26, 2026 09:41
@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Jun 26, 2026
Signed-off-by: Matteo Collina <hello@matteocollina.com>
@mcollina mcollina force-pushed the doc-vfs-not-sandbox branch from 914cd5c to 4ca53e7 Compare June 26, 2026 09:50
@mcollina mcollina requested a review from aduh95 June 26, 2026 09:55
@jojin1709

Copy link
Copy Markdown

Thanks for the quick doc update. For reference, I also filed #64129 which covers a related but distinct issue in MemoryProvider — backslash characters in paths are converted to forward slashes before normalization, which allows .. traversal within the virtual tree. Not sure if that warrants a separate doc note or fix, but flagging it here in case it's relevant

@mcollina mcollina added the commit-queue Add this label to land a pull request using GitHub Actions. label Jun 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

commit-queue Add this label to land a pull request using GitHub Actions. doc Issues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants