Laravel Mix VS laravel-debugbar

Yeah, I'm the guy who tells you: No one is forcing you to switch to Vite. Laravel Mix still works and will work for the forseeable future. Mix isn't even part of the Laravel GitHub organisation and noone from the core Laravel team has contributed to the package in the last few months.

"It is fixed." https://github.com/mikaelbr/node-notifier/issues/361 via https://github.com/laravel-mix/laravel-mix/issues/2937 via https://github.com/josephdyer/skeleventy/issues/32

A quick Google search led me to here. Which suggested that I add the following to my webpack.mix.js file:

I've found a workaround and raised an issue (https://github.com/JeffreyWay/laravel-mix/issues/3045)

Oh, have I got the thing for you. You can just use laravel-mix for the common usecases:

Try laravel-mix, makes it a lot easier.

Let's not forget the time webpack did this but only on Mondays to cut down on spam, causing builds to fail on Mondays

https://github.com/JeffreyWay/laravel-mix/issues/2550#issuecomment-752735914

debugbar And n+1 query

tldr using debugbar is a good point, everything else is just use laravel when using laravel and avoid n+1 problem

Nice but I can get the same functionality with the debugbar - what makes this better?

We then used platform-specific performance analysis tools to determine which of these endpoints needed the most attention. The highest-traffic sites we needed to optimize used Laravel, a popular PHP framework. We used Laravel Debugbar to analyze those web apps.

Try installing laravel-debugbar, it will show you which parts of the app are slow (e.g. boot up vs views), which queries are slow, and how many queries run (helpful when you forgot to eager load some models).

I wanted to tweak Laravel Debugbar, so it could also work with any JSON API, but I ended up writing a minimal package of my own to do the trick.