Laravel Blade highlighting works! ... partially

[MannyFay]

Hi,
I have found a super weird behavior in (my?) Nvim (setup?). ...I'm not 100% sure, if this is the right place to post this question, but I have no idea where to ask it else.

I was using Packer plugin manager all the time for my Nvim setup. Now I have had time to put thoughts into my setup and switched to Lazy. Cool, by the way. Super fast and straight forward. I like it a lot.
Now here is my problem...

One part of my work is to write code in a PHP/Laravel environment. Blade is the PHP templating engine they use. The my-file.blade.php files are for the front end (you can compare it with HTML structure). If I open this kind of files, there is no syntax highlighting at all.
If I search for one of these Blade files with Telescope, the syntax highlighting works in Telescopes preview pane.
If I use another color scheme -> same problem.
If I throw my config and use kickstarter.nvim -> same problem.
If I open a regular HTML file highlighting works.
If I use my Packer config, highlighting works in file and Telescope preview.

Has anybody an idea why this happens??

Manny

[muneebusmani]

i just made a separate repo for my laravel configuration in lazyvim just clone the repo, remove .git/ , add your keymaps and you are good to go:
https://github.com/muneebusmani/laravel
there are some prerequistes for setting up phpstan + psalm for each laravel project, you have to first install these:
https://github.com/barryvdh/laravel-ide-helper
https://github.com/psalm/psalm-plugin-laravel
https://github.com/larastan/larastan
(follow all of their readme instructions)

install these three composer packages locally in your project or just make a script for automating this task and add that to $PATH
then you will get the best out of neovim
note that you wont get intellisense when you use this in your blade files:
{{ some php code}}
because there is no official lsp for blade yet, just workarounds

dont mind the README.md in that repo because i also made my own config out of someone else's repo, i forgot to update that guys readme, i optimized it only for laravel so you could just add an alias

alias laravim="NVIM_APPNAME=laravim nvim"

put this line in your ~/.zshrc or ~/.bashrc
choose whatever name you like for the alias and folder

[MannyFay]

Thank's :) I will take a look on it after work!!

[muneebusmani]

idk how Jetbrains does it but the kinda have the intellisense for each and everything for laravel blade etc in phpstorm, even though i never pay for these kinda shit, but still Jetbrains ides are pretty slow compared to neovim (if configure properly)

[MannyFay]

Yes, absolutely! They are super slow. I don't like their IDEs and tools and I don't need that overkill, just Blade syntax highlighting like in my Packer setup is enough for me...

[MannyFay]

@muneebusmani - Thank's for the help. I've tried out the Laravel/LazyNvim repo.
It is way to overloaded for me. I don't like the LazyNvim Neovim configuration at all.
I've read all the PHP/Laravel stuff in it, so there is one question coming up: Why it works in my personal Packer plugin manager Neovim configuration without all this stuff, and if I use Lazy plugin manager not???
Does it really depends on the plugin manager?? Sounds not logical for me..

To make a rework in the PHP/Laravel LazyNvim files and directories to fit my configurations, the amount of time is absolutely insane. So by this, I will stay with my Packer environment till I see there a solution.

[MannyFay]

"Dude, here is the thing.." 🤣 I like you ^^ 🫶

Yes, I think you're absolutely right, and I think, that I came back again to it.

But for now, it takes too long to rewrite my whole Nvim configuration into that kind of deep after my regular working hours.
My actual Nvim setup is very stable and I can use it for my work properly.

With family and the regular living stuff I think, I need about around a month or longer to solve this. Meanwhile I can't do anything else about building knowledge in IT.
So I have to choose my time wisely 😜

[muneebusmani]

I have a suggestion just use your packer as it is and start implementing and testing things you have implemented in packer to lazy, just start little by little, if you start from scratch it would take really long as you have very busy schedule I suggest slowly slowly read the docs of LazyVim(the nvim distro) and lazy.nvim(the package manager) to learn and implement the things you did with packer, learn the differences in plugins specification and other stuff, once you got everything ready, just transition to it, and btw about syntax highlights, blade doesn't has an official syntax highlighting so there are ppl who created treesitter compatible syntax highlighting, if you wanna know how did it work just add the treesitter.lua I have in plugins folder and copy after/ and queries/ folders from my repo root and put in your config root and then do :TSInstall blade

[muneebusmani]

Btw why don't you do laravel with react/vue as it is much better than laravel live wire blade

[MannyFay]

Thought the same, but the Laravel team says in their documentation:

[muneebusmani]

you didn't read the topic below, did you?
https://laravel.com/docs/11.x/frontend#inertia
read this