Decouple Nest's DI container from Node API about nest

[aventez]

AFIAK Nest's DI container isn't something that was designed to live outside of nestjs, and so changing it to support v8 only would be hard.

Probably it was - https://docs.nestjs.com/standalone-applications

why not using alternatives like tsyringe? I believe you could build an API similar to NestJS on top of it

We use Inversify and that's the only option, but having all the rest NestJS features just can be great

[micalevisk]

why not using alternatives like tsyringe? I believe you could build an API similar to NestJS on top of it

AFIAK Nest's DI container isn't something that was designed to live outside of nestjs, and so changing it to support v8 only would be hard.

[micalevisk]

still, it's a nodejs framework

asking to support v8 only or anything not related with nodejs seems out of the scope of the fw to me

[KostyaTretyak]

@aventez, try the DI used in Ditsmod. It can work completely independent of Ditsmod. It is built on the basis of the Angular v4.4.7 native module.

import { Injector, injectable } from '@ditsmod/core';

class Service1 {}

@injectable()
class Service2 {
  constructor(service1: Service1) {}
}

@injectable()
class Service3 {
  constructor(service2: Service2) {}
}

const injector = Injector.resolveAndCreate([Service1, Service2, Service3]);
const service3 = injector.get(Service3);
service3 === injector.get(Service3); // true
service3 === injector.resolveAndInstantiate(Service3); // false

[kamilmysliwiec]

Thanks for your suggestion!

There are no plans to implement it in the foreseeable future.

If you think your request could live outside Nest's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.