This is outside of the scope of Intelephense and likely requires a better Blade plugin. Hopefully, this will get better with the official Laravel plugin when it's released.

Sometimes they conflict with each other a little, but you can use them simultaneously. They both have additional features missing in the other so it can be helpful. However, I have occasionally run into performance issues with phpactor.

Doesn't work for me either. I wonder if that's an issue with the Treesitter grammar or something else.

Thank you for the kind words! You can always update the keybindings to something like: keys = { { "<leader>aa", ":Laravel artisan<cr>" }, { "<leader>ar", ":Laravel routes<cr>" }, { "<leader>am", ":Laravel related<cr>" }, }, For the error with service "laravel.test" is not running seems like an issue with either Herd or Laravel Sail. Are you using Sail?

Thanks Lars! A .env.test file is a great solution and that’s what I typically use. There’s many ways to do it though and I just wanted to point out that you don’t want your tests making actual requests to the API.

Good article, never realized there wasn’t an equals validation rule. I wonder if that’s something that should be in Laravel by default? Is it a use case you’ve run into often?