I believe that passing all of the paths through this function will fix this issue, in fact I have tested it locally and will file a PR. I am optimistic we can solve this together 🙂
Escaping ! will mean that users will not be able to use glob features. So I think it is on user to escape patterns if they do not need to use glob feature.
I am working in a next.js project with a page at path
/pages/[...rest.tsx]
which follows next's guidance for catch-allsHowever when running size-limit on the build artifact from my project I get an error like
I believe this is due to how size limit is calling globby. globby (more specifically, fast-glob) expects you to escape your paths before passing them over. fast-glob even provides a helper for this.
I believe that passing all of the paths through this function will fix this issue, in fact I have tested it locally and will file a PR. I am optimistic we can solve this together 🙂