Allow a Regex in createFilter

[dtothefp]

It seems annoying to have to learn the intricacies of the mini-match API in order to include and exclude especially for people who are transitioning from a tool like Webpack, where Regex is used a lot.

This is especially useful for I would think a not uncommon use case of an internal NPM registry containing un-compiled es6 modules. In Webpack for the babel-loader I'm able to use the regex below in the exclude field:

/^.+\/node_modules\/(?!@hfa\/).+\.jsx?$/

To only compile internal es6 modules in the @hfa namespace. Maybe this is possible with a combination of include and exclude using minimatch but doesn't seem user friendly to not be able to re-use regex that I'm using with another tool. In the above example I feel minimatch would be overcomplicated because you need to account for modules inside @hfa that may have their own internal dependency on an @hfa module and so on, being sure to only compile the source of each module and not an commonjs module dependency inside of the @hfa or nested @hfa node_modules directory. Would you be open to allowing regex and/or minimatch string as input to createFilter? If so, I'd be happy to put a PR together.

[dtothefp]

@Rich-Harris any suggestions on this?

[Rich-Harris]

@dtothefp sorry, just saw this. Would gladly accept that PR! 😀

[jetiny]

@Rich-Harris is this ok ?

[Rich-Harris]

This can finally be closed – v2.0.0 (major version change, so plugins will need to upgrade) supports regexes. Thanks

[dtothefp]

Cool, thanks!! 👍