InversifyJS | lightweight inversion of control container | Dependency Injection library

You're almost there. You're getting undefined because this in your decorator is undefined and should be referring to an instantiated instance of your target. Changing that definition to a regular function call instead of an arrow function should do the trick.

In order for container.get() to work, must be bound to the container at some point. In your composition root (where you set up your container) you can create this binding:

No, and that's actually by-design.

The whole point of DI is that there are no surprises with how your program is configured: everything you configure in ConfigureServices (your in your case, SetupDi) is exactly what you get at runtime. By using attributes to configure DI then that would introduce "non-local effects" and it would be much harder to track-down bugs introduced by incorrect or misconfigured dependencies caused by an errant attribute.

(To that extent, I disagree with Angular's design - but that's off-topic).

(I also feel that .NET Core's DI system is also imperfect - too many necessary details are hidden behind DI injection extension-methods that you need to use ILSpy or Reflector to peer into).

As a workaround, you can "test" your DI services at app startup to ensure everything is configured by reflecting over every IService in your project and trying to instantiate the implementation.

Here's the code I use in my ASP.NET and ASP.NET Core projects to verify DI is thoroughly configured: