Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
mock-fs compatibility
See original GitHub issueEnvironment
- OS Version: macOS 10.13.3
- Node.js Version: 8.9.4
Actual behavior
I’ve written a gulp-like file transformer to glob for files, read them, modify them, and write them back to the file system. I’ve also included delete functionality. As this functionality can be highly dangerous when there’s a bug, I test using mock-fs.
I had been using globby, but switched to using fast-glob directly. When I was using globby v7 (backed by node-glob) I was able to use mock-fs. Now, using fast-glob, I get ENOENT errors thrown.
Expected behavior
Allow file-system to be mocked for testing using something like mock-fs or by passing a mock file system object to fast-glob as an option.
Steps to reproduce
- git clone https://github.com/shannonmoeller/ygor.git
- cd ygor
- npm it
Sample Code
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
nvm, it may well have been a change in mock-fs but I went ahead and bumped the
usepackage in snapdragon and published 0.8.2 with that change. You will need to reinstall everything and to make sure NPM uses that version you’ll also need to delete package-lock.json files.Confirming this update fixed the issue. Thanks again!