-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Too many directories are scanned with multi-patterns #77
Comments
What I cannot get my head around is: With this pattern: And this cwd: The result of And it will search our complete But why are we not directly searching this as a root? |
the old root optimizer didn't run if the pattern started with |
Runs smoothly! Thanks for your work! |
EDIT: (Leaving the comment for completeness) Somehow this options
Will skip the _ANOTHER folder:
Due to exclude() most likely |
@fabianwohlfart FYI the newest release |
yes works nuxt/nuxt#30137 (comment) |
If I have two patterns like this
and a folder structure like this
not only the app and utilities folder are searched, but also the
should-not-matter
folder.This leads to huge performance breakdowns, if not only one, but many folders are »in between«.
I came to this behavior through a weird warning in
Nuxt
, where suddenly my build process increased from 500ms to 25seconds.nuxt/nuxt#30137
I tracked it down to a
scanDirectory
function inunimport
, that took longer than expectedunjs/unimport#401
I came to the conclusion that they recently switched from
glob
totinyglobby
Yet
glob
only takes a few milliseconds, buttinyglobby
takes seconds to scan everything.Here is a reproduction.
https://github.com/fabianwohlfart/test__nuxt-layers-slowdown
You can simply go to the app folder and run the
tinyglobby.mjs
, you will see that it searches the foldershould-not-matter
, which it shouldn't.The text was updated successfully, but these errors were encountered: