-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Expose internalBinding fs_dir #37746
Comments
Just FYI - there is an initiative already underway to deprecate userland access to |
Thx for the information. |
Could this issue be reconsidered, please? @3cp @cjihrig If not, can someone tell me, how is tschaub/mock-fs#358 issue will be solved? |
The way mock-fs works is too fragile. |
Is your feature request related to a problem? Please describe.
tschaub/mock-fs#319
mock-fs
works through replacing Nodejs internal binding forfs
.We encountered a technical blocker when implementing
fs.opendir
inmock-fs
because the new internalBindingfs_dir
is not exposed inprocess.binding('fs_dir')
.Describe the solution you'd like
We would like to suggest to expose
fs_dir
binding here, so that we could replace it at runtime inmock-fs
.node/lib/internal/bootstrap/loaders.js
Lines 73 to 107 in 7296bcb
Describe alternatives you've considered
N/A
The text was updated successfully, but these errors were encountered: