Would be useful.

node-glob has the nonull option which instead of returning an empty array if no patterns matches, it returns the patterns that didn't match anything. This can be useful when you want to report to the user what patterns/filepaths couldn't be found.

Definitely needs a better name than nonull though.

I am a little confused on how and when to use memfs, unionfs, linkfs, patchFs, patchRequire, jest-plugin-fs etc.

There are a lot of pieces to make a great vehicle but the instructions on how assembling them together are not well organized. A lot of documentation is sparse across different repos and issues on those repos. Outdated info in old issues and changes in the state of the

Description

This link
http://jsfiddle.net/gh/get/library/pure/fnndsc/ami/tree/master/lessons/00#run
Is on the main page and ends up with a error 422?

Live Demo

Its in master above.

Steps to Reproduce

Follow the link

Expected Results

Loader example in jsfiddle as in the past.

Browsers Affected

• All
• Chrome
• Firefox
• Edge
• Sa

We have a few branches in fs.writeFile that aren't being tested: https://codecov.io/gh/filerjs/filer/src/master/src/filesystem/implementation.js#L1850. To fix this, we need a few more tests added:

• test that passes invalid flags to options.flags (i.e., doesn't include w)
• test that passes a number for the data argument to write, and expects to have it written as a string.

Following this discussion in CE2 repo, I create an issue here for a new unifile feature

As services like dropbox offer an API to search files and folders (names and content and metadata), I would like to add a search box in CE2 for such services (not for t

if I do a thing like

const copy = require('copy');

const files = ['dist/**/*','README.md','LICENSE.md'];
copy(files, '/tmp/folder', (err, files) => {
 // handle result here 
})

Result :

• README.md and LICENSE.md are located in /tmp
• The content of the dist folder is in '/tmp/folder'

Should be :

• README.md and LICENSE.md are located in /tmp/folder
• T

It would be really great if the README made it clear that this package requires git to be on the path as well as carrying the "experimental" and "doesn't work on Windows" warnings which are shown on github. This would help make sure that devs who discover the package on www.npmjs.org are aware of these limitations before they spend time trying to try out the package.

Thanks.