-
Notifications
You must be signed in to change notification settings - Fork 64
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
[Feature] Replace glob with fast-glob for .*proj file search in project-graph calculation #410
Comments
Sounds good to me. Do you care to throw a PR together for this? If you've done it locally, it shouldn't be too much trouble. Use the same version of fast-glob we use in Nx; there are some regression bugs in the latest version. |
Sure, will try to open a PR tomorrow! 👍 |
Regardless of the swap to fast glob, we should do option 2 eventually as well. Nx does this during project inference, but we should adhere to it as well. |
🎉 This issue has been resolved in version 1.9.11 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Is your feature request related to a problem? Please describe.
When trying to introduce nx with nx-dotnet to a large existing solution with about 70 projects, I figured out that the project graph calculation took several minutes. By debugging the nx-dotnet plugin I found out that the glob search for .*proj files took about 3 minutes, due to the fact that I did not use the nx dist dir as output directory but the normal bin directory within the project directory to avoid to much changes to the repository structure and build architecture for now.
Describe the solution you'd like
['**/bin/**', '**/obj/**']
, it is possible to speed up the calculation even more: fast-glob took 15 Sec. whereas glob took ~35 Sec.Describe alternatives you've considered
Changing the output directories to the normal nx dist directory could be an option to speed up the execution, but that would possibly interfere with our current build architecture and would cause more concerns from some developers against introducing nx workspace.
The text was updated successfully, but these errors were encountered: