You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to get mock-fs working with webpack for a while. I'm not sure if mock-fs is not designed for a browser, but I'm trying to get webpack's dir-loader working with mocks.
It doesn't seem to be working and there are no instructions so I'm assuming this is not possible. Please let me know if there is support or plans for support for browser testing using mock-fs.
The use case is that I'm writing an electron app that works offline and uses js-git so I am hoping to use mock-fs to abstract out file operations and to speed up by development cycle since electron is quite slow to refresh and develop on.
Also, unless I'm missing something, it seems a little strange that a mocking library would depend on the original implementation.
The text was updated successfully, but these errors were encountered:
@kmalakoffmock-fs relies heavily on Node's fs module, patching it only to provide a swappable binding (the result of process.binding('fs')).
It may actually not be that much more work to provide overrides for every fs function, but when this project started, I was attracted to the smaller API exposed by the binding.
I've been trying to get mock-fs working with webpack for a while. I'm not sure if mock-fs is not designed for a browser, but I'm trying to get webpack's dir-loader working with mocks.
It doesn't seem to be working and there are no instructions so I'm assuming this is not possible. Please let me know if there is support or plans for support for browser testing using mock-fs.
The use case is that I'm writing an electron app that works offline and uses js-git so I am hoping to use mock-fs to abstract out file operations and to speed up by development cycle since electron is quite slow to refresh and develop on.
Also, unless I'm missing something, it seems a little strange that a mocking library would depend on the original implementation.
The text was updated successfully, but these errors were encountered: