Dissect Laravel Package

Product Decisions This Supports

• Code Analysis & Tooling: Enables building custom static analysis tools (e.g., linters, formatters, or IDE plugins) for PHP/Laravel projects without relying on external CLI tools (e.g., PHPStan, Psalm).
• Custom Syntax Highlighting: Powers syntax-aware features (e.g., IDE extensions, code editors, or documentation generators) by parsing PHP/Laravel syntax into structured data.
• Lexical/Syntactical Validation: Validates custom syntax rules (e.g., enforcing Laravel-specific conventions like route naming, service container bindings, or Eloquent relationships) in CI/CD pipelines.
• Build vs. Buy: Justifies in-house tooling for niche use cases where existing packages (e.g., PHP-Parser) lack Laravel-specific features or require heavy customization.
• Roadmap: Supports future-proofing for projects needing deep PHP/Laravel code introspection (e.g., auto-generating API docs, detecting deprecated Laravel patterns, or optimizing queries).

When to Consider This Package

• Adopt if:

  • You need fine-grained control over PHP/Laravel syntax parsing (e.g., for a custom compiler, refactoring tool, or DSL).
  • Existing tools (e.g., PHP-Parser, nikic/PHP-Parser) are overkill or lack Laravel-specific abstractions.
  • Your team has PHP/Laravel expertise to extend the package (low stars suggest niche adoption).
  • You’re building internal developer tools (e.g., a Laravel IDE plugin) and want to avoid vendor lock-in.

• Look elsewhere if:

  • You need ready-made solutions (e.g., use PHPStan for static analysis or Laravel Pint for formatting).
  • Your use case aligns with highly maintained packages (e.g., vlucas/phpdotenv for env parsing).
  • You lack bandwidth to integrate and maintain a low-star package long-term.
  • Your project relies on modern PHP features (e.g., attributes) that may not be fully supported.

How to Pitch It (Stakeholders)

For Executives: "This package lets us build custom PHP/Laravel tooling in-house—think of it as Lego blocks for parsing and analyzing code. For example, we could automate Laravel-specific validations in CI or power a next-gen IDE plugin. It’s lightweight (MIT-licensed) and avoids vendor lock-in, but requires PHP expertise to assemble. Ideal for niche needs where off-the-shelf tools fall short."

For Engineering: *"Dissect is a low-level PHP parser for lexical/syntactical analysis. Use it if you’re:

• Extending PHP-Parser with Laravel-specific rules (e.g., parsing route definitions).
• Building a custom compiler (e.g., for a Laravel DSL or macro system).
• Avoiding CLI dependencies in internal tools (e.g., a self-hosted code quality scanner). Tradeoff: Low stars mean less community support, but the MIT license and pure PHP design make it flexible. Pair with php-parser for broader compatibility if needed."*