Code Style Pint Laravel Package

Product Decisions This Supports

• Laravel 13 Compatibility: Enables seamless adoption of this package in projects upgrading to Laravel 13, particularly for teams using ArtisanPack UI or Laravel Boost with hybrid WordPress/Laravel workflows. Eliminates dependency conflicts that could block migrations to Laravel 13.
• Future-Proofing Hybrid Stacks: Aligns with long-term Laravel roadmaps, ensuring WordPress/Laravel integration projects remain maintainable as Laravel evolves. Critical for headless WordPress backends, plugin APIs, and multi-platform microservices.
• ArtisanPack Ecosystem Synergy: Strengthens compatibility with downstream packages (e.g., artisanpack-ui/code-style-pint), reducing friction for users relying on the full ArtisanPack toolchain.
• Build vs. Buy Clarity: Reinforces the "buy" decision for teams needing WordPress spacing rules without maintaining custom PHPCS-Fixer configs, now with explicit Laravel 13 support.
• Use Cases (Updated):
  • Laravel 13 migrations with WordPress integrations (e.g., REST API plugins, theme backends).
  • Agency projects transitioning clients to Laravel 13 while preserving WordPress compatibility layers.
  • Open-source projects dependent on illuminate/support (e.g., custom Laravel packages with WordPress hooks).

When to Consider This Package

• Adopt if:
  • Your team is migrating to Laravel 13 and needs WordPress-style spacing rules for hybrid projects (e.g., plugins, themes, or API integrations).
  • You rely on ArtisanPack UI or Laravel Boost and require Laravel 13 compatibility for your code style tooling.
  • Your project uses illuminate/support (directly or indirectly) and must support Laravel 10–13 without dependency conflicts.
  • You prioritize zero-maintenance PHPCS-Fixer presets for WordPress conventions in Laravel 13+ environments.
• Look elsewhere if:
  • Your codebase is pure Laravel/PHP with no WordPress dependencies and no plans to upgrade to Laravel 13 (the change is purely additive).
  • You need Laravel 12 or below exclusivity (this package now supports 13, which may introduce subtle behavioral changes in illuminate/support).
  • Your team prefers minimalist spacing and finds WordPress-style rules irrelevant to your Laravel 13+ stack.
  • You require custom PHPCS-Fixer rules that conflict with the package’s Laravel 13-dependent defaults (e.g., illuminate/support behavior changes).

How to Pitch It (Stakeholders)

For Executives: "This minor update unlocks Laravel 13 support for our WordPress/Laravel code style package, ensuring smooth migrations for hybrid projects. For teams adopting Laravel 13—especially those using ArtisanPack UI—this eliminates dependency roadblocks while maintaining WordPress compatibility. It’s a low-risk, high-reward upgrade: no new features, just future-proofing for modern Laravel stacks. Think of it as ‘Laravel 13 readiness’ for your WordPress-integrated PHP codebases."

For Engineering: *"Laravel 13 users: This update widens illuminate/support to support v13, so:

• No more blocked installs: Use --wordpress flag in Pint without Laravel version conflicts.
• ArtisanPack UI compatibility: Future-proofs your code style tooling for Laravel 13 upgrades.
• Hybrid projects: Still enforces WordPress spacing (if ( ), [ ]) alongside Laravel 13’s latest conventions. Update with composer update artisanpack-ui/code-style-pint—it’s a silent fix for a potential migration headache."

For Developers: *"Laravel 13 + WordPress devs: Good news—this package now plays nicely with Laravel 13!

• Run php artisan artisanpack:publish-pint-config --wordpress as usual; Laravel 13 is now supported.
• Fixes dependency issues for projects using illuminate/support in Laravel 13.
• Zero changes to your workflow, just broader compatibility. Update your composer.json and keep formatting hybrid codebases without friction."