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
I cannot have two modules with same name in application. Is this a bug or a feature? #3362
Comments
For example, I can have two variables in different Node.js modules. Or even in different NPM packages. I want to have different Nest.js modules with same name, but in different NPM packages. And what are benefits of this limitation? Maybe I can override any module in an application? This is not obvious. And I can have two or more DYNAMIC modules with same name in application. |
See #3363 |
@kamilmysliwiec |
It should fix your problem :) We'll merge it shortly. |
Awesome! Thank you! |
I actually encountered the same problem with providers sharing the same name instead of modules. |
Fixed in the latest release (modules with the same name) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Current behavior
I cannot have two modules with same name in application. Only the first module will be available in the application. In my case, this is the
AModule
from "./my-a-module".Input Code
Third party library
My code
Expected behavior
I am not sure if this is a bug. But I was expecting that I could have two separate Nest modules with same name.
Environment
The text was updated successfully, but these errors were encountered: