With the addition of PRs like nodejs/node#48658 or nodejs/node#49593 virtual filesystem overlays are in an uncomfortable position where Node both doesn't respect anymore its own APIs (ie fs). We currently workaround that by patching some primitives from process.binding('fs'), but this is untenable, even at short term (nodejs/node#50687).
We often heard that "one of our goals is to allow mocking of modules, including of builtins; but only via loaders". That's fine to me, but given the recent acceleration of PRs aiming to shortcut fs it suggests now is the time to start discussing in details what such an overlay would look like that would satisfy everyone.
With the addition of PRs like nodejs/node#48658 or nodejs/node#49593 virtual filesystem overlays are in an uncomfortable position where Node both doesn't respect anymore its own APIs (ie
fs). We currently workaround that by patching some primitives fromprocess.binding('fs'), but this is untenable, even at short term (nodejs/node#50687).We often heard that "one of our goals is to allow mocking of modules, including of builtins; but only via loaders". That's fine to me, but given the recent acceleration of PRs aiming to shortcut
fsit suggests now is the time to start discussing in details what such an overlay would look like that would satisfy everyone.