-
Notifications
You must be signed in to change notification settings - Fork 522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: node-patches\filesystem patcher. #1332
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Left some questions & suggestions. :)
2fb38c5
to
fd25fb9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
The npm_packages
and associated node_patches
target can go in a follow up PR as they are not being used and we should integrate the testing into the bazel in a follow PR as well and use the "checked-in file" rule to ensure the check-in js files up to date.
as integration will happen in another pr.
This reverts commit 9795e68.
new package which patches the fs module of node core such that it will not follow links out of a root directory path.
for the nodejs startup script. prevents links from escaping the sandbox