Minko Gechev outlined what’s next for Angular, touching on "Implicit Imports" and "Signal-based Inputs". Meanwhile, Matthieu Riegler explored the realities of contributing to Angular, and Thomas Laforge delivered an in-depth look at dependency injection in the framework.
Implicit Imports
Francesco Ciulla's livestream featured Minko Gechev, Angular's product lead. While the session served mostly as a gentle intro to version 17, Gechev teased an "implicit import" capability that could arrive later.
With it, you would list the TypeScript import at the top of the file alone, skipping the one in the component's decorator entirely.
Unsurprisingly, the community caught wind of this on X right away, sparking the usual debate over advantages and drawbacks.
Signal-based Inputs
Minko Gechev made another appearance, this time on the ThisDotMedia livestream alongside Brandon Roberts, Enea Jahollari, and Deborah Kurata. During the conversation, he hinted that a Signal-based input could land in version 17.2.
Beyond that, he peeled back the layers on the team's internal workflow, detailing the extensive coordination required to bring partners, libraries, and the broader ecosystem on board so that updates remain safe and non-disruptive.
Enea Jahollari raised a notable observation regarding the new Angular website's codebase. It turns out that angular.dev doubles as a reference implementation for what a modern Angular app should look like, and Minko added that the team plans to strip out zone.js from it the moment the framework makes that feasible.
Becoming an Angular Contributor
Matthieu Riegler joined the AngularAir podcast to share advice on how to get started as a contributor to the framework. His insights were valuable, but he also issued a caution about the dangers of introducing breaking changes.
Every major breaking change needs to be handled by the Angular team. With the sheer volume of Angular apps running inside Google, that task is unmanageable. The team heavily depends on schematics to automate these migrations, and any PR that brings a breaking change must also ship the corresponding schematic.
Deep-Dive DI
Thomas Laforge has put together an in-depth write-up on dependency injection. While it may not be immediately clear, multiple injector types exist beyond the common ones.
These include the PlatformInjector, the NullInjector, and, naturally, the RootInjector. Setting aside time to go through his work is definitely worth the effort.
Medium