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

investigate on optimizing picomatch's bundle size #121

Open
SuperchupuDev opened this issue Sep 24, 2024 · 2 comments
Open

investigate on optimizing picomatch's bundle size #121

SuperchupuDev opened this issue Sep 24, 2024 · 2 comments

Comments

@SuperchupuDev
Copy link

zeptomatch is 4x smaller than picomatch in terms of bundle size and does pretty much the same, analyzing zeptomatch's optimizations and pr'ing them to picomatch could result in a much smaller bundle size which would be a huge win considering how widely used the package is

@SuperchupuDev SuperchupuDev changed the title investigate into optimizing picomatch's bundle size investigate on optimizing picomatch's bundle size Sep 24, 2024
@43081j
Copy link
Collaborator

43081j commented Sep 25, 2024

You're right

If the maintainers are not open to it, we could also just start moving everyone over to zepto

@SuperchupuDev
Copy link
Author

doing so would be hard as zeptomatch is esm only

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

No branches or pull requests

2 participants