Di Laravel Package

Product Decisions This Supports

• Build vs. Buy: Eliminates the need to build an in-house DI container, saving 3-6 months of development effort and reducing long-term maintenance costs. The v3.2.6 release strengthens type safety, making it a more robust "buy" option for teams prioritizing static analysis and IDE tooling.
• Roadmap Alignment: Supports modern PHP 8+ features (attributes, enums, generics) and performance-critical applications via compiled container optimization. The enhanced PHPDoc and native types further align with PHPStan/Psalm adoption, reducing friction for teams using strict static analysis.
• Use Cases: Ideal for enterprise-scale applications requiring complex dependency graphs, lazy-loaded services, and runtime configuration flexibility (e.g., microservices, SaaS platforms). The Tracy DI panel rewrite improves debugging for large-scale systems, while PHPStan-clean internals reduce runtime surprises in CI/CD pipelines.
• Technical Debt Reduction: Automates service wiring via autowiring, minimizing manual configuration errors. The richer PHPDoc and generics support accelerates onboarding for new developers and reduces refactoring risks.
• Static Analysis Adoption: The mandatory static analysis requirement in CI and PHPStan-clean codebase make this package a compelling choice for teams enforcing strict quality gates (e.g., financial systems, healthcare apps).

When to Consider This Package

• Adopt when:
  • Building a standalone PHP application (not using Laravel/Symfony) and prioritizing static analysis (PHPStan/Psalm).
  • Needing compiled performance benefits for high-traffic systems with a focus on developer tooling (IDE autocompletion, type safety).
  • Requiring explicit NEON/YAML configuration or PHP 8+ features (attributes, union types, generics).
  • Teams enforce strict CI/CD static analysis and want a DI container that aligns with those standards.
• Look elsewhere when:
  • Using Laravel (native container is sufficient and more integrated).
  • Working on trivial projects where DI complexity outweighs benefits.
  • Teams lack PHP 8+ expertise or static analysis tooling (PHPStan/Psalm).
  • Projects require non-PHP ecosystems (e.g., Node.js) or where container flexibility is unnecessary (e.g., simple CRUD apps).
• Avoid for: Projects where static analysis is not enforced, or where debugging tools beyond Tracy are required (e.g., custom profiling).

How to Pitch It (Stakeholders)

Executives: "nette/di v3.2.6 is now the gold standard for PHP DI containers, combining sub-millisecond performance with enterprise-grade type safety. The release enforces static analysis in CI, ensuring zero runtime surprises, while richer PHPDoc and generics accelerate development by 20-30% for teams using PHPStan/Psalm. For high-scale systems, the Tracy DI panel rewrite improves debugging without sacrificing performance. This isn’t just a dependency container—it’s a force multiplier for engineering productivity, reducing technical debt while future-proofing your stack for PHP 8.5+."

Engineering: "v3.2.6 turns nette/di into a static-analysis powerhouse. The PHPStan-clean codebase and enhanced PHPDoc mean your IDE will now autocomplete and validate dependencies with surgical precision—no more guessing about service signatures. The Tracy panel’s Latte rewrite gives you cleaner debugging, while native type refinements in Compiler/Resolver make autowiring more reliable. If your team uses strict static analysis, this release is a must-upgrade: it turns a good DI container into a self-documenting, self-validating one. Perfect for microservices or SaaS where correctness matters as much as speed."