Skip to content

Conversation

@SamAsEnd
Copy link
Contributor

This PR introduces a mechanism to significantly improve the developer experience by guiding users to correctly place development-only dependencies into the require-dev block. When a package is internally tagged with the new "dev" keyword, and a user attempts to install it using composer require without the --dev flag, Composer will now intelligently prompt them:

The package you required is recommended to be placed in require-dev (because it is tagged as "testing") but you did not use --dev.
Do you want to re-run the command with --dev? [yes]?

This PR introduces a mechanism to significantly improve the developer experience by guiding users to correctly place development-only dependencies into the require-dev block.
When a package is internally tagged with the new "dev" keyword, and a user attempts to install it using composer require without the --dev flag, Composer will now intelligently prompt them:
```
The package you required is recommended to be placed in require-dev (because it is tagged as "testing") but you did not use --dev.
Do you want to re-run the command with --dev? [yes]?
```
@SamAsEnd
Copy link
Contributor Author

Here is the composer implementation this "dev" tag will affect

@taylorotwell taylorotwell merged commit 0a438bc into laravel:main Oct 28, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants