Services
Upgrade the frameworks you already run
An old Symfony, Laravel, or React app can stay where it is. The work is a path through versions, tests, and the parts the product still depends on.
WordPress, Magento, and the rest of that list are the same kind of job. We name the version you run, the version you need, and the behavior that must not change on the way.
When it fits
- The version you run is behind, and a package or a host you need no longer supports it.
- Upgrades keep getting postponed because nobody is sure what will break.
- The app runs on Symfony, Laravel, WordPress, Magento, TypeScript, or React, and it should stay there.
How the work goes
- We read the lockfile, the framework release notes, and the tests you already trust.
- We write down what has to keep working: checkout, sign-in, the admin, and the job that runs after midnight.
- The move is one boundary at a time. Symfony and Laravel follow their upgrade guides. WordPress and Magento get a staging copy before themes or plugins move. TypeScript and React get a new compiler target and a pass over the screens people use.
- The staging copy is clicked through against the list from step two before the release goes out.
Example: pick the framework
Version path
Pick the framework you already run. The behavior that must survive stays on the note.
What you receive
- A written path from the version you run to the version you will run
- A staging copy close enough to production to trust a click-through
- The next feature shipped on the new version, by the same team
How to start
Send the framework, the version you run, the version you need, and the parts that must keep working. Email it to info@developerlab.nl, or see the contact page for other ways to reach Puya Sarmidani.
Send an email