Laravel Homestead是否自动添加依赖？未装doctrine/dbal仍可删列

Great question! Let’s unpack why this happened, since it’s a common point of confusion with Laravel migrations and Homestead.

First, let’s confirm the official documentation: Laravel does require the doctrine/dbal package for modifying or dropping columns in migrations. This package handles schema introspection and cross-database compatibility, which Laravel relies on to safely alter existing table structures. That part of the docs is accurate.

Now, as for why it worked on your Homestead setup, here are the most plausible reasons:

• Indirect dependency installation: You didn’t add doctrine/dbal directly to your composer.json, but another package in your project (like a third-party Laravel package, or even some Laravel ecosystem tools) lists it as a required dependency. Composer automatically installs all indirect dependencies when you run composer install or composer update, so it ended up in your vendor folder without you explicitly requiring it.
• Pre-existing package files: If you cloned a project that already had doctrine/dbal installed, or if you previously installed it and didn’t fully remove it (even after deleting it from composer.json), the package might still exist in your project’s vendor directory. Homestead doesn’t clear your project’s local dependencies automatically.
• Global environment? Unlikely: Homestead is a pre-configured VM with core tools like PHP, Nginx, and databases, but it does not install project-specific Composer dependencies globally for your Laravel apps. Your project’s dependencies are always managed locally via your project’s composer.json.

To confirm which scenario applies to you, run this command in your project directory inside Homestead:

composer show doctrine/dbal

If the package is installed, this will display details including which other package required it (look for the "required by" line in the output).

Homestead doesn’t automatically add all Laravel dependencies to your project—it just provides a consistent, pre-configured environment where your project’s Composer dependencies are resolved as they would on any other development setup.

内容的提问来源于stack exchange，提问作者Chukwuebuka