Vadims Daleckis

`semantic-release` should publish it automatically, hmmm, but it looks like it does not, I'll take a look.

with regards to `globby`: How do you tell it to use `memfs`?

Published manually under `2.7.1`, will take a look at `globby`.

`fast-glob` internally uses `readdir-enhanced` and that seems to work: ```js const glob = require('globby'); const {Volume} = require('../lib/volume'); const {patchFs} = require('fs-monkey'); const {ufs} = require('unionfs'); const fs = require('fs');...

`fast-glob` does not seem to work with `memfs`, don't know why, giving it up for now.

@vjpr is there a minimal reproducible example? Because if I do this ```js const { Volume } = require('../src/volume'); const vol = new Volume; vol.mkdirpSync('./app'); vol.writeFileSync('./app/foo.json', 'foo') vol.symlinkSync('./app', './app/foo') console.log('fs',...

So the Windows paths work correctly when `process.platform === 'win32'`, in Webpack on Windows `process.platform === 'win32'` should be `true`. So it should already work on Windows. Or is there...

To write tests for Windows, my first try would be: 1. Create a separate test suite for Windows. 2. At the very beginning, before importing anything, set `process.platform = 'win32'`....

Haven't had time to read this thread properly, I will do it later, but just wanted to mention one thing. Path handling in Node and `memfs` is done using `path`...

For testing with Jest, you can check out `mrm-core`, here they mock the file system: - https://github.com/sapegin/mrm-core/blob/master/__mocks__/fs.js And here you can see `memfs` volume is reset after each test: -...