$ the-wire · showcase
LARAVEL SERVE COMMAND BREAKS HOST-PORT PARSING
By RepoJournal · Filed · About Laravel · Composed from the cited sources · methodology
3 people shipped this
The IPv6 detection logic in Laravel's serve command is mangling localhost:8888 style addresses, splitting them incorrectly and breaking local development.
The 13.x branch shipped a regex fix [1] that restores proper host-and-port parsing in the serve command. The bug was subtle: `preg_match` returns 0 on no match (not false), so the IPv6 branch was catching IPv4 and hostname inputs with ports. If you've been debugging why `php artisan serve --host=localhost:8888` stopped working as expected, this is your fix [2]. Meanwhile, package-skeleton pulled a critical fix [3] for the `configure.php` script, which was crashing when GitHub repository creation failed. The script was reaching for a `message` key that never existed, causing a fatal error on a failed GitHub API call [4]. Both are one-line fixes masking real edge-case handling gaps. Moat received a routine bump to its GitHub Actions release plugin [5], nothing critical there.
Action items
- → Pull the serve command fix into 13.x if you're running development with port-specific hosts laravel/framework [plan]
- → Update package-skeleton if you publish new packages laravel/package-skeleton [plan]
References
- [1] [13.x] Fix host port parsing in serve command ↗ laravel/framework
- [2] Fix host port parsing in serve command (#60828) ↗ laravel/framework
- [3] Fix null message when GitHub repository creation fails ↗ laravel/package-skeleton
- [4] fix null message when GitHub repository creation fails (#29) ↗ laravel/package-skeleton
- [5] chore(deps): bump softprops/action-gh-release from 3.0.1 to 3.0.2 in the github-actions group ↗ laravel/moat
