Replace Mix with Vite as build tool

[SteelWagstaff]

The dev team has used Vite instead of Mix/Pressbooks Build Tools for the last two plugins they've created. We replace should update Pressbooks Build Tools to use Vite and use it consistently across all our maintained repos.

DoD:

• Research the use of Vite for build processes across all Pressbooks repo
• Write a brief report/recommendation for team to agree on
• Prepare Pressbooks Build Tools 5.0.0 release that uses the recommended approach

Resources

https://github.com/laravel/vite-plugin/blob/main/UPGRADE.md#migrating-from-laravel-mix-to-vite
https://christoph-rumpel.com/2022/6/moving-a-laravel-webpack-project-to-vite
https://creagia.com/blog/using-laravel-vite-with-bootstrap-and-sass

[greatislander]

Might be worth considering Vite.js as well— it's now the standard tool for Laravel.

[SteelWagstaff]

Thanks Ned — Os and Dalcin used Vite for build process in our new network catalog plugin and I think would be interested in considering it for build processes elsewhere as well. We’ll be discussing options in our next product meeting.

[SteelWagstaff]

We're also using Vite in the new pressbooks-multi-institution plugin.

[arzola]

cc @cmurtagh

[arzola]

I've been working on this ticket the main components for this upgrade are:

1. JS Pressbooks build tools
2. Vite Bridge (previously presbooks/mix) Helper functions for PB/themes
3. Updating each theme/plugin to use the tools above.

One thing to consider is that we've been using https://github.com/kucrut/vite-for-wp in our new plugins because it has a nice DX for development that works nicely on docker and it provides automatic swap between watcher/hotreload, probably we should take advantage of (Vite Bridge) package and wrap vite-for-wp with our custom config, this way also we will fix the dependency updates hell of https://github.com/kucrut/vite-for-wp when they release a new version because it will be wrapped in our library.

I want to discuss this with the team before moving forward.

[arzola]

I have this working for themes and our private plugins, I'm still working on Pressbooks that has a complex enqueuing assets handling 😅