Make Composer available via npm run on host machine

[paulbonneau]

Context

Working on a ticket on my wordpress-develop cloned instance, I wanted to lint and format my code but :

• I couldn't find the command in composer.json in order to do so;
• I didn't want to install composer nor phpcs on my host machine because those tools are already available in the container spawned.

Solutions

To lint my code I used this command : node ./tools/local-env/scripts/docker.js run -T --rm php composer lint [my_file]

@SirLouen suggested to create a new custom script in package.json enabling developers to directly invoke the composer instance of the wordpressdevelop/php container from their host machine. Implementing this will simplifies future call to composer specific scripts from host machine (linting, formating etc ...).

You will find the modified package.json in the attached .diff and the PR related to this ticket.

[paulbonneau]

63912

[paulbonneau]

corrected diff for 63912-2.diff

[SirLouen]

Hey @paulbonneau
Why not using a similar format as the current env:cli command like:

node ./tools/local-env/scripts/docker.js exec php composer

## Context
Working on a ticket on my wordpress-develop cloned instance, I wanted to lint and format my code but :

• I couldn't find the command in composer.json in order to do so;
• I didn't want to install composer nor phpcs on my host machine because those tools are already available in the container spawned.

##Solutions
To lint my code I used this command : node ./tools/local-env/scripts/docker.js run -T --rm php composer lint [my_file]

​@SirLouen suggested to create a new custom script in package.json enabling developers to directly invoke the composer instance of the wordpressdevelop/php container from their host machine. Implementing this will simplifies future call to composer specific scripts from host machine (linting, formating etc ...).

Trac ticket: (https://core.trac.wordpress.org/ticket/63912)

[paulbonneau]

Replying to SirLouen:

Hey @paulbonneau
Why not using a similar format as the current env:cli command like:

node ./tools/local-env/scripts/docker.js exec php composer

Hello @SirLouen !
I kept docker run over docker exec because it enables the container to be spawned specifically at the command runtime meaning that you can for example, lint your code, even if wordpressdevelop/php container is off.

Thank for your review !

[SirLouen]

Replying to paulbonneau:

I kept docker run over docker exec because it enables the container to be spawned specifically at the command runtime meaning that you can for example, lint your code, even if wordpressdevelop/php container is off.

Good idea. I think this is good to go.

[SergeyBiryukov]

In 60803:

Build/Test Tools: Make Composer available via npm run on the host machine.

This enables developers to directly invoke the Composer instance of the wordpressdevelop/php container from their host machine, making it easier to call Composer-specific scripts: linting, formatting, etc.

Props paulbonneau, SirLouen.
Fixes #63912.