$ the-wire · showcase
MULTIPLEX SHIPS INLINE MODE FOR NON-TTY ENVIRONMENTS
By RepoJournal · Filed · About Laravel · Composed from the cited sources · methodology
![laravel-nightwatch-permissions[bot]](https://avatars.githubusercontent.com/u/958072?v=4)
Multiplex v0.2.1 now runs inline when piped or invoked from CI instead of failing, making it viable for Makefiles and automated tooling.
Multiplex hit two releases overnight to nail down a critical gap: v0.2.0 added inline fallback mode for non-TTY environments [1], letting you pipe output or run from a Makefile without errors. But v0.2.0's publish test exposed a timing bug where exit signals fired before buffered output drained from pipes, causing commands to lose their final lines entirely [2]. v0.2.1 patches that by holding the exit handler until both stdout and stderr close with a 500ms grace period [3]. Across Laravel proper, framework work continues on job timeout visibility [4], allowing you to distinguish between worker timeouts and job-level failures when listening to JobTimedOut events. Boost continues hardening its installation flow with v2.5.3, now skipping the guideline discovery prompt when run via composer scripts [5], stopping every `composer update` from blocking on interactive input even in automated contexts.
Action items
- → Upgrade to Multiplex v0.2.1 if you pipe output or use inline mode in CI laravel/multiplex [plan]
- → Update Boost to v2.5.3 to prevent composer script blocking laravel/boost [plan]
- → Review JobTimedOut listener logic to use new timeout field for worker vs job diagnosis laravel/framework [monitor]
References
- [1] v0.2.0 ↗ laravel/multiplex
- [2] Wait for a command's output to drain before reporting its exit ↗ laravel/multiplex
- [3] v0.2.1 ↗ laravel/multiplex
- [4] [13.x] Add the timeout in JobTimedOut ↗ laravel/framework
- [5] v2.5.3 ↗ laravel/boost
