Question About LSP Roadmap and Potential Blade LSP Support

[tu6ge]

Feature

Hi 👋

First of all, thank you for your great work on Mago. It’s exciting to see that LSP support is planned for the upcoming 2.0 release. I believe this will significantly improve the PHP development experience, especially for developers using VS Code.

I have a question regarding your LSP roadmap.

Since Mago is planning to introduce LSP capabilities, I’m wondering:
1. Do you have any plans to extend LSP support beyond PHP syntax/formatting into template ecosystems such as Laravel Blade?
2. Would Blade template support fall within the scope of Mago’s LSP goals?
3. Is there any high-level roadmap or design direction you could share about the LSP implementation?

I am currently considering building an LSP server specifically for Laravel Blade templates, and I’m trying to understand whether:
• This would overlap with your future plans, or
• It would make sense to develop it as a separate, complementary project, or
• There might be an opportunity to collaborate.

My goal is to improve the development experience for Laravel developers in editors like VS Code, and I’d love to align with your direction if possible.

Thanks again for your work, and I appreciate any insight you can share about the roadmap.

Best regards

Example

[azjezz]

Hi!

Yes, we do have plans to support both twig and blade ( #303, #304 ), However:

1. This won't be any time soon ( it will be long after 2.0 is released )
2. The twig and blade support are going to be mainly for the formatter and linter, I really doubt we will integrate it with the analyzer.

[AJenbo]

It sounds like we’re all thinking along the same lines :)

• It would make sense to develop it as a separate, complementary project, or

While you could provide basic feedback and compleation for Blade with a standalone LSP you would fall a bit short when it comes to the PHP portion you would fall short without an LSP that both Laravel and Blade.

About a month ago, I started working on an LSP in Rust and ended up using Mago as the parser, only to realize that they do have plans for LSP support in the future.

I already have solid support for PHP and Laravel, including completion, definition, signature help, and hover.
(See the table in the README: https://github.com/AJenbo/phpantom_lsp?tab=readme-ov-file#features)

I’m also the maintainer of Bladestan (a Blade plugin for PHPStan), and my plan is to improve standards for Blade files both through my LSP and Bladestan. You can find my roadmap for adding Blade support to the LSP here: todo-blade.md

Overall, my goal is correctness and performance, assuming a modern PHP stack using Composer. You can also find the reasoning behind my design decisions in ARCHITECTURE.md and todo-laravel.md.

I think my LSP is alrady very viable, but I hope to at least inspire others in this field to make excellent tools for PHP.

P.s. I would be happy for testing, feedback, and contributions.