$ the-wire · showcase
LARAVEL TOOLING TIGHTENS PROTOCOL COMPLIANCE ACROSS LSP AND EDITORS
By RepoJournal · Filed · About Laravel · Composed from the cited sources · methodology
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)
2 people shipped this
The Laravel language server shipped protocol-compliant shutdown handling while Sublime and Zed extensions hardened their marketplace presence.
LSP v0.0.29 lands with proper shutdown lifecycle support [1], implementing the null response and exit notification sequence the protocol demands. This matters because editor integrations have been ignoring malformed shutdowns, and now the server will correctly reject subsequent requests after shutdown [1]. The Sublime extension [2] simultaneously addressed Package Control review feedback by adding command-palette settings access, excluding tests from packages, and silently disabling in non-Laravel projects. Meanwhile, the Zed extension is splitting into official and community variants [3], with the official build landing as `laravel-official` in the marketplace to avoid collision. All three repos shipped 8 commits and 3 PRs across the day, consolidating months of editor work into shipping-ready form.
Action items
- → Update Laravel LSP to v0.0.29 in your editor config laravel/lsp [plan]
- → Install Sublime LSP-Laravel from Package Control once it appears laravel/sublime-extension [monitor]
- → Switch to laravel-official Zed extension if using the community version laravel/zed-extension [plan]
References
- [1] Implement protocol-compliant LSP shutdown lifecycle ↗ laravel/lsp
- [2] Address Package Control review feedback ↗ laravel/sublime-extension
- [3] Prepare official Laravel marketplace listing ↗ laravel/zed-extension
