[wp-trac] [WordPress Trac] #62807: Protect `env:start` command against connection issues

[WordPress Trac]

#62807: Protect `env:start` command against connection issues
------------------------------+-----------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:
------------------------------+-----------------------------

Comment (by iamadisingh):

 Currently, the composer update command is run as part of the `env:start`
 npm script in `package.json`

 {{{
 "env:start": "node ./tools/local-env/scripts/start.js && node ./tools
 /local-env/scripts/docker.js run -T --rm php composer update -W",
 }}}

 To provide a clearer, actionable error message, we could move the
 `composer update` logic into the JS startup script `start.js`. This would
 allow us to run Composer using Node's spawnSync, check the exit code, and
 print a custom message if it fails (something like "There was a failure
 running composer update. This is often caused by network issues or
 Packagist.org downtime. Please check your internet connection and try
 again.").

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62807#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform