People searching “Laravel Boost update” run npm update and expect the Vue guidelines to change. Boost is a Composer dev dependency. The Boost guide is the install. This page is the command after you bump Inertia or Laravel.
TL;DR
- boost:update rewrites the agent guidelines for the versions you installed.
- Boost is not an npm package.
- Do not hand-edit a paragraph you need to keep inside a file the next update overwrites.
- Do not put a provider API key in
boost.json.
The fix#
composer require laravel/boost --dev
php artisan boost:updateboost:install is the first time. boost:update refreshes the guideline files and the MCP config for the packages now in composer.json. Restart the coding agent after it runs so the agent reads the new files.
The docs say those generated files can be gitignored, because the commands rewrite them. Do not hand-edit a paragraph you need to keep inside a file the next update overwrites. Put a project rule in your own file.
What to avoid#
Gotcha
Do not put a provider API key in boost.json. Do not add Vue Router or Ziggy because an old guideline mentioned them. The stack guide is the current choice.
FAQ#
How do I update Laravel Boost after you upgrade?
boost:update rewrites the agent guidelines for the versions you installed. Boost is not an npm package.
What goes wrong with Laravel Boost update?
Many developers run npm update and expect the Vue guidelines to change. Do not hand-edit a paragraph you need to keep inside a file the next update overwrites.
