Please describe the minimum necessary steps to reproduce this issue:

The example given in README for API some is not working as intended.
Link to example in REPL

const mm = require('micromatch');
// mm.some(list, patterns[, options]);

console.log(mm.some(['foo.js', 'bar.js'], ['*.js', '!foo.js']));
// true
console.log(mm.so

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.

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.

Similar to micromatch/glob-base#5

One test fails,

  1) should get a base path: qmarks::

      AssertionError: '?' == '.'
      + expected - actual

      -?
      +.
      
      at Context.<anonymous> (/home/pravi/forge/debian/git/pkg-javascript/node-parse-glob/test.js:364:12)
      at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
      at Tes

Feature request

Feature description

We should provide a social share widget-style element on the tool that allows the user to share the short-link for the tool (do.co/glob-tool) via social media or copy the link directly their clipboard.

How the feature is useful

Currently, the tool has very little on it that pushes the user to share it on -- we should encourage users to sha