Laravel Mix VS WordPress Packagist

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

If I have to use WordPress for something, I'll build it as a standard PHP project, requiring WordPress and any themes/plugins as a Composer dependencies from johnpbloch/wordpress and WordPress Packagist (more info here). If I need to do any significant templating, I like to use Timber.

Use it together with https://wpackagist.org/ and you can update all plugins/themes by latest or by version number.

Another option you can look at is Bedrock by Roots - that is sets WP as an app with composer already set up. It allows you to install WP plugins (from official WP repo) via composer (WP Packagist). The structure is set up to allow for git workflow. Also helpful if you want to make use of a bunch of composer packages on your site.

https://wpackagist.org/ in the example you see "repositories", now in that array you can put your plugins github-link and set the other settings. with composer install you install them and with composer update you update them

Side question: I know that the WordPress ecosystem has been moving toward better support for Composer – e.g., with WPackagist. But wouldn't plugins installed/updated via Composer run into the same issue?