Micael Levi L. Cavalcante

What if you remove that `setTimeout` call?

then I don't think that that code is enough to reproduce your issue, right? Please share the full code along with the steps to reproduce. ## [why reproductions are required](https://antfu.me/posts/why-reproductions-are-required)

@linkFly6 this GH Issue is still open, so no. I didn't investigate it further yet. Feel free to do so.

btw that was not a regression because of this:  but yeah, looks like we need to improve it

@iannak PRs are more than welcomed

nestjs will infer the provider token using parameter's metadata. Prior to this, such metadata is always ignored when using `Inject` on parameters because nestjs always use either the supplied token...

regarding that, it will behave just like property-based injection. For them, the `@Inject()` is used due to introspection limitations. For constructor-based ones, we'll start supporting `@Inject()` for completeness sake only

I'm not sure about the API I found that `pathBeforeVersion` flag a bit hacky (like a patch over something) and not flexible. As versioning is a first-class thing in nestjs,...

still, the `abortOnError: false` doesn't let us to capture that exception. So I believe that this is a bug.

I was thinking of another API for this I believe yours is better 1. `UniqueModuleFactory.for('myFirstDynamic', MyDynamicModule.forRoot('123', 'hello'))` 2. `UniqueModuleFactory.forModule(MyDynamicModule.forRoot('123', 'hello'), 'myFirstDynamic')` --- Another concern of mine: does [module re-exporting](https://docs.nestjs.com/modules#module-re-exporting) still...