- Is frosh/shopware-rector a Laravel package?
- No. frosh/shopware-rector targets Shopware 6 and depends on rector/rector, nikic/php-parser, and Shopware core classes; it has no Laravel service provider or runtime role. For a Laravel-only portfolio, the evaluation stops here. Use it only as a dev-time static-analysis tool in Shopware repositories.
- How do I install frosh/shopware-rector in a Shopware 6 plugin?
- Install it as a dev dependency with composer require --dev frosh/shopware-rector, commit a rector.php config per Shopware repo, and run vendor/bin/rector locally and in CI. Pin it together with rector/rector and Shopware core constraints, then start with the narrowest rule set. Installation is trivial; configuration and diff review are the real work.
- Which Shopware versions and migration paths does frosh/shopware-rector cover?
- The package targets Shopware 6.x with migration-oriented rules for legacy and plugin code, but the provided context does not spell out exact edges such as 5-to-6, 6.5-to-6.6, or 6.6-to-6.7. Check the rule sets, README, and Packagist constraints before planning a version wave. Do not assume coverage for a specific upgrade until you verify it in a pilot branch.
- Does it refactor Shopware apps, plugins, and themes or only PHP code?
- Rector rewrites PHP source through an AST, so this package is for PHP code in Shopware plugins and themes, not services.xml or storefront JavaScript. The blurb covers plugin and theme code migrations; Shopware app structures and XML/JS changes need separate checks. Review which rule sets apply to your plugin layout before running a bulk migration.
- What Rector version does frosh/shopware-rector require?
- It depends on rector/rector, but the exact Rector major constraint is not stated in the supplied context. Pin rector/rector and frosh/shopware-rector together, check Composer and Packagist, and align with PHP 8.1+. Rector majors have breaking changes, so version skew can cause config failures or silently skipped rules.
- Can I use frosh/shopware-rector in CI with PHPStan and PHP-CS-Fixer?
- Yes. It is a developer-time static-analysis tool, so require-dev plus a committed rector.php and a CI step is the intended integration, alongside PHPStan and PHP-CS-Fixer. There is no application-layer coupling or runtime overhead. Establish a Rector baseline first so existing violations are frozen and only new changes fail CI.
- How do I avoid false positives when Rector rewrites Shopware code?
- Use dry-run first, review every diff, and require a green test suite before merging. Start with the narrowest applicable rule set, expand set by set, and apply changes plugin by plugin behind PRs rather than one bulk commit. Do not run migration rule sets on a dirty tree, and freeze a baseline to limit noise.
- Is frosh/shopware-rector safe for production Shopware upgrades?
- Treat it as adopt with guardrails: it is useful for repetitive Shopware migrations, but maturity signals are weak with 48 stars, 0 dependents, and a single-maintainer community org. It is not a runtime dependency, so keep it in require-dev and pin versions. False positives can compile but misbehave, so dry-run, diff review, and tests are mandatory.
- What are alternatives to frosh/shopware-rector for Shopware migrations?
- The context does not name direct alternatives. Compare it with manual Shopware upgrade work, Shopware migration guides, custom Rector rules, and your existing PHPStan/PHP-CS-Fixer checks. Laravel-focused Rector sets or Laravel Shift are not substitutes because this tool targets Shopware 6.
- Who maintains frosh/shopware-rector and is there commercial support?
- It is maintained under FriendsOfShopware, a community org adjacent to the Frosh agency, and the context flags a single-maintainer signal and limited field validation. A commercial support path via Frosh is not confirmed here; ask Frosh directly. Release cadence is not stated, and the listed last release date of 2026-08-13 should be reconciled against Packagist before you rely on it.