How can scoped dependency injection help properly manage the specific lifecycle of dependencies that should genuinely only exist for the duration of a particular feature or a specific user session, rather than living for the entire lifetime of the whole application?

Scoped dependency injection lets you register certain dependencies within a more narrowly defined scope, such as specifically for the duration of a user's currently active checkout flow or their currently authenticated session, rather than every single dependency necessarily needing to exist and remain in memory for the entire lifetime of the whole running application, and properly disposing of that entire scope, along with all of the dependencies registered specifically within it, once that particular feature or session genuinely ends helps meaningfully reduce unnecessary ongoing memory usage and ensures that stale, no longer relevant data does not continue lingering unnecessarily in memory longer than it should.

getIt.pushNewScope(scopeName: 'checkout');
getIt.registerSingleton<CheckoutSession>(CheckoutSession());

// When checkout completes
getIt.popScope();