Typo3 Rector Laravel Package

Product Decisions This Supports

• Accelerated TYPO3 Upgrades: Enables rapid migration between TYPO3 versions (e.g., v10 → v14) by automating deprecation fixes, reducing manual effort by 70-80% for core and extension code.
• Cost-Effective Maintenance: Justifies build vs. buy for legacy TYPO3 projects by eliminating the need for costly third-party migration services.
• Roadmap Alignment: Supports TYPO3’s LTS (Long-Term Support) strategy by ensuring compatibility with new releases (e.g., v14) while maintaining backward compatibility for older versions.
• Use Cases:
  • Legacy Modernization: Migrate TYPO3 v7–v12 projects to v14+ with minimal downtime.
  • Extension Compatibility: Automate fixes for custom extensions during TYPO3 core upgrades.
  • Pre-Upgrade Audits: Identify deprecated code before manual refactoring (via --dry-run).
  • CI/CD Integration: Enforce coding standards post-rector runs (e.g., ECS) to maintain clean code.

When to Consider This Package

Adopt if:

• Your project uses TYPO3 v7–v14 and requires upgrades/migration.
• You have custom extensions or overrides needing TCA/Fluid/TypoScript updates.
• Your team lacks dedicated dev resources for manual migration (saves 100+ hours per major version).
• You prioritize risk mitigation by validating changes pre-production.

Look elsewhere if:

• Your project is TYPO3 v15+ (package supports up to v14).
• You need non-PHP file migrations (e.g., TypoScript/FlexForm) → Use fractor instead.
• Your codebase is highly customized with unsupported TCA structures (e.g., missing ctrl/columns keys).
• You lack version control or CI/CD pipelines to test changes safely.

How to Pitch It (Stakeholders)

For Executives: "TYPO3 Rector automates 70–80% of the manual work required to upgrade TYPO3, reducing migration costs by $50K–$200K per project. For example, a client upgrading from v10 to v14 could save 3–6 months of dev time while ensuring zero downtime. It’s a force multiplier for our TYPO3 team, letting them focus on innovation instead of busywork."

For Engineering: *"This is Rector for TYPO3—a PHP refactoring tool that:

1. Auto-fixes deprecations (e.g., $TYPO3_CONF_VARS → $GLOBALS['TYPO3_CONF_VARS']).
2. Supports incremental upgrades (e.g., apply v10 rules before v14).
3. Integrates with ECS for clean code output.
4. Safety-first: Always --dry-run before production. Example: Upgrading a v12 extension to v14 takes 1 command (vendor/bin/rector process) instead of days of manual hunting for deprecated APIs. We’ll need to:

• Add ClassAliasMap to composer.json for cross-version compatibility.
• Run it per extension in CI before merging.
• Pair with ECS to enforce standards post-rector."*

For DevOps: *"Add this to your TYPO3 upgrade pipeline:

# GitHub Actions example
- name: Run TYPO3 Rector
  run: |
    composer require --dev ssch/typo3-rector
    vendor/bin/rector process --dry-run  # Validate changes
    vendor/bin/rector process            # Apply (post-review)
    vendor/bin/ecs check                 # Enforce standards

Key: Never run on production. Use --dry-run to preview changes and test thoroughly in staging."*