-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Slow AppModule Dependencies Initialization After Upgrading to NestJS 11 #14552
Comments
Please provide a minimum reproduction repository. You can start one by running why reproductions are required |
We can't help you without seeing your |
Hi @micalevisk and @kamilmysliwiec, I'll be creating a private repository. Please share an email address so I can grant you access. |
Please provide a minimum public reproduction repository (Git repository/StackBlitz/CodeSandbox project). |
@marefati110 you could create a private repo here on github and add me as contributor using my username |
I've set up a private registry for the project and added you. |
@marefati110 please upgrade also, just for sanity sake, make sure that |
Current behavior
Description
After upgrading my project from NestJS 10 to 11, I noticed that the AppModule dependencies initialization step has become significantly slower.
Actual Behavior
The initialization process in NestJS 11 is much slower compared to NestJS 10.
NestJS 11:
Minimum reproduction code
https://github.com/nestjs
Steps to reproduce
No response
Expected behavior
The application should initialize AppModule and its dependencies as quickly as in NestJS 10.
No significant performance degradation should occur due to the upgrade.
nestjs10:
Package
@nestjs/common
@nestjs/core
@nestjs/microservices
@nestjs/platform-express
@nestjs/platform-fastify
@nestjs/platform-socket.io
@nestjs/platform-ws
@nestjs/testing
@nestjs/websockets
Other package
No response
NestJS version
No response
Packages versions
Node.js version
v22.12.0.
In which operating systems have you tested?
Other
No response
The text was updated successfully, but these errors were encountered: