Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to micromatch@4 or picomatch #154

Closed
mrmlnc opened this issue Jan 31, 2019 · 2 comments
Closed

Move to micromatch@4 or picomatch #154

mrmlnc opened this issue Jan 31, 2019 · 2 comments

Comments

@mrmlnc
Copy link
Owner

mrmlnc commented Jan 31, 2019

We have a big problem related to package require time (#92). This issue is related to micromatch, which has a very large number of dependencies.

About micromatch@4:

Also micromatch/picomatch has a problem:

@mrmlnc mrmlnc added this to the 3.0.0 milestone Jan 31, 2019
@mrmlnc mrmlnc changed the title Move to micromatch 4 or picomatch Move to micromatch@4 or picomatch Jan 31, 2019
@mrmlnc
Copy link
Owner Author

mrmlnc commented Feb 18, 2019

https://github.com/terkelg/globrex to compare performance and minimatch

@jonschlinkert
Copy link

@mrmlnc fwiw I just pushed up picomatch v2.0: https://github.com/micromatch/picomatch/tree/dev. I also got it completely ported to micromatch, and I'm now working on docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants