You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then the composer.lock need to have packages and packages-dev populated.
Error the composer.lock have a packages-dev empty, this causes that development packages get installed when running composer update --no-dev. All the require-dev dependencies are merged, but included in packages instead of packages-dev.
If the requre-dev is only present in one composer.json runs the expected behaviour.
The text was updated successfully, but these errors were encountered:
marcoslois
changed the title
Invalid composer.lock when requires-dev present on more than once composer.json
Invalid composer.lock when the same requires-dev dependency is present on more than once composer.json
Apr 18, 2016
Composer determines if a given package is a dev mode dependency by
running a solver with dev mode disabled and diffing the result against
the full solver run. This causes every run to two emit
`InstallerEvents::PRE_DEPENDENCIES_SOLVING` events: one with dev mode
enabled and one without. Previously we were using the global dev mode
state set by the main install/update/dump event for both calls. This led
Composer to believe that all conflicting pacakges processed by
composer-merge-plugin were non-dev requirements and an unexpected
composer.lock state for later `composer install --no-dev` executions.
Closeswikimedia#113
Composer determines if a given package is a dev mode dependency by
running a solver with dev mode disabled and diffing the result against
the full solver run. This causes every run to emit two
`InstallerEvents::PRE_DEPENDENCIES_SOLVING` events: one with dev mode
enabled and one without. Previously we were using the global dev mode
state set by the main install/update/dump event for both calls. This led
Composer to believe that all conflicting pacakges processed by
composer-merge-plugin were non-dev requirements and an unexpected
composer.lock state for later `composer install --no-dev` executions.
Closeswikimedia#113
Composer determines if a given package is a dev mode dependency by
running a solver with dev mode disabled and diffing the result against
the full solver run. This causes every run to emit two
`InstallerEvents::PRE_DEPENDENCIES_SOLVING` events: one with dev mode
enabled and one without. Previously we were using the global dev mode
state set by the main install/update/dump event for both calls. This led
Composer to believe that all conflicting pacakges processed by
composer-merge-plugin were non-dev requirements and an unexpected
composer.lock state for later `composer install --no-dev` executions.
Closeswikimedia#113
Given two composer.json files, root/composer.json:
root/mods/test/composer.json:
When running composer update
Then the composer.lock need to have packages and packages-dev populated.
Error the composer.lock have a packages-dev empty, this causes that development packages get installed when running composer update --no-dev. All the require-dev dependencies are merged, but included in packages instead of packages-dev.
If the requre-dev is only present in one composer.json runs the expected behaviour.
The text was updated successfully, but these errors were encountered: