Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Typo3 Rector Laravel Package

ssch/typo3-rector

TYPO3 Rector applies instant upgrades and refactoring to TYPO3 website and extension code, easing migrations between releases and removing deprecations. Extending Rector, it supports PHP 5.3+ and requires PHP 7.4+. Always run on development environments under version control, never production.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • TYPO3 Version Upgrades: Automate migration from older TYPO3 versions (v7–v14) to newer ones, reducing manual effort and risk of breaking changes. Aligns with roadmap goals for modernization. Latest releases add targeted rules for Extbase annotation → attribute migrations and schedulable command attributes, closing gaps in modern-version upgrades.
  • Code Quality & Compliance: Enforce modern TYPO3 coding standards (e.g., dependency injection, explicit globals) to improve maintainability and reduce technical debt. The new CodeQuality preset (enabled via structarmed ^0.17) gives teams a one-switch baseline for stricter, consistent code.
  • Build vs. Buy: Avoid reinventing migration tools; leverage this package to accelerate upgrades instead of hiring developers for manual refactoring. Continued investment (new rectors, bugfixes each release) means the buy option keeps compounding in value versus maintaining an in-house tool.
  • Extension Maintenance: Streamline updates for TYPO3 extensions by automating deprecation fixes (e.g., GeneralUtility::makeInstance, ExtensionUtility calls, annotation-to-attribute rewrites). Bugfixes like the corrected MigrateLabelReferenceToDomainSyntaxRector reduce manual triage for extension authors.
  • DevOps Efficiency: Integrate into CI/CD pipelines to validate code changes pre-merge, catching deprecated patterns early. Adopting the CodeQuality preset makes CI gates more consistent without per-project rule curation.

When to Consider This Package

  • Adopt if:

    • Your project uses TYPO3 v7–v14 and needs to upgrade to a newer version.
    • You maintain custom extensions or core TYPO3 code requiring refactoring—especially code still using Extbase annotations (now migratable to attributes).
    • Your team lacks bandwidth for manual migration but prioritizes code quality.
    • You want a ready-made quality baseline (via the structarmed / CodeQuality preset) rather than curating Rector rules yourself.
    • You’re using PHP 7.4+ and can integrate Rector into your workflow.
  • Look elsewhere if:

    • Your project uses TYPO3 v15+ (limited support for newer versions).
    • You need to migrate non-PHP files (e.g., TypoScript, Fluid templates)—use fractor instead.
    • Your codebase is highly customized with unsupported patterns (validate with --dry-run first).
    • You lack coding standards tools (e.g., ECS) to format Rector’s output.

How to Pitch It (Stakeholders)

For Executives: "This tool automates the bulk of the manual work needed to upgrade TYPO3, cutting migration time from weeks to days. By enforcing modern coding standards—now with a built-in quality preset—it reduces long-term maintenance costs and aligns our tech stack with best practices, without requiring a full rewrite. The project is actively maintained with frequent feature and bugfix releases, so our investment keeps paying off. The risk is minimal: we run it in a dev environment, review changes, and deploy incrementally."

For Engineering: *"TYPO3-Rector is a Rector-based refactoring tool tailored for TYPO3. Recent releases add:

  • Annotation → attribute migrations (TYPO3\CMS\Extbase\Annotation → attributes).
  • Schedulable command attribute migrations (AddAsNonSchedulableCommandAttributeRector).
  • Version-specific upgrades (e.g., TYPO3 v10→v14).
  • Code quality via the CodeQuality preset (bundled with structarmed ^0.17), plus deprecation fixes like GeneralUtility::makeInstance → constructor injection. Integrate it into your CI pipeline for pre-commit checks or use it as a one-time migration tool. Pair it with ECS for clean output. Start with --dry-run to validate changes before applying them, and track releases—most are additive feature/bugfix drops with low upgrade friction."

Key Metrics to Highlight:

  • Time saved: Automates hours/days of manual refactoring, now covering annotation-to-attribute migrations.
  • Risk reduction: Catches breaking changes early in dev; active bugfix cadence (e.g., corrected label-reference migration) improves reliability.
  • Cost efficiency: Avoids hiring contractors for migration work; the built-in CodeQuality preset reduces setup effort.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
steadrun/laravel-monitor
labyrinthe/connect-laravel
elmogy/layan
drewdan/sentinel-client
dskripchenko/laravel-llm
fatryst/nuonuo
stevenay/myanfont
gmostafa/php-graphql-client
xeviant/paystack
snowsoft/faker
meditationsteps/blogetc
animalyoung/laravel-influxdb
onix-solutions/sms-telera
lonely-lights/prosetta
oxygen/data
oxygen/core
jengo/base
xiloryx/log-collector
a21ns1g4ts/filament-stripe
la-php/laravel-admin