What changes does Laravel Boost make to the installation flow in Laravel 13?

Answered by 2 creators across 3 videos

As Laravel Daily explains, Laravel Boost changes the installation flow in Laravel 13 by handling the upgrade steps automatically and at a different point in setup. A key change is that the Boost upgrade now runs after npm install, letting Boost detect newly installed packages and apply the upgrade path in one pass. In addition, Boost 2.3.x adds an upgrade path prompt that guides you through upgrading the framework and related packages, aiming for a smooth transition with minimal breaking changes and no required application code changes for starter kits in the initial pass. The upgrade flow is positioned to deliver a quick green test run, focusing on compatibility and automation rather than deep code edits during the initial install. As Nunomaduro highlights, Boost can automate the upgrade from Laravel 12 to 13 with the slashupgrade v13 command, making the process simpler even if manual checks are still advised. While Laravel Shift offers a deeper, reviewable modernization path, Boost prioritizes speed, compatibility, and a streamlined initial setup. Altogether, the installation flow shifts from a purely manual upgrade to an AI-assisted, post-npm-install upgrade with guided prompts, reducing manual steps and accelerating a first-pass upgrade.

As Laravel Daily points out, Boost upgrade now triggers after npm install, enabling it to detect newly installed packages during setup.
Laravel Daily also notes that Boost 2.3.x includes an upgrade path prompt to guide users through upgrading the framework and related packages.
In the same Laravel Daily upgrade video, the change is framed as aiming for a smooth flow with minimal breaking changes and no required app-code changes for starter kits in the initial pass.
Nunomaduro’s livestream emphasizes that upgrading to Laravel 13 can be automated with Boost via the slashupgrade v13 command, simplifying the dependency and config updates.
In the comparison video, Boost is described as focusing on quick, compatible upgrades (green tests) whereas Shift provides deeper skeleton and codebase updates, reinforcing that Boost changes the installation flow toward speed and automation.