Skip to content

"A script would override a Composer command and has been skipped" warnings #418

@aleksblendwerk

Description

@aleksblendwerk

Steps required to reproduce the problem

  1. Add a custom script in the scripts section of composer.json
  2. Run composer normalize

Expected Result

Successfully normalized ./composer.json.
Updating lock file.
Loading composer repositories with package information
[...]

Actual Result

Successfully normalized ./composer.json.
Updating lock file.
A script named qa would override a Composer command and has been skipped
Loading composer repositories with package information
[...]

Not a big deal at all but is there any way to suppress these warnings? I am about to include composer-normalize into our CI process and team mates might think something is wrong when seeing those.

From what I see it's due to Composer's Application->doRun() running twice and the second time around the scripts have already been defined.

I am on Composer version 1.10.05 right now.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions