In store for 2.0: build and tooling updates

[DaneEveritt]

This is less so a feature request, and more a list of known changes we're planning on making when releasing 2.0 to help alleviate some consistent requests and track these changes somewhere visible.

1. Removal of twin.macro — replacing with generic TailwindCSS (and upgrading tailwindcss to v4) classes and standard shared components.
2. Replace jest with vitest. Should be trivial given the complete lack of existing front-end testing, but vitest will be nice to use moving forward with components.
3. Replace phpunit with pest so that our tests align closely in style between the front-end and back-end. Additionally my professional experience has shown pest to be easier to organize and reason about since you can do describe/it blocks pretty nicely where phpunit lacks this. Pest is backed by PHPUnit so this shouldn't be too terrible of an upgrade and we don't have many tests (different issue...).
4. Replace webpack with vite, and replace yarn with pnpm.
5. Replace swr with tanstack-query.

[cesarmr-github]

I think for 2.0, since almost all of the code will have to be touched. It's a good time to implement a language system

[KingIronMan2011]

There already is a language system, but no translations other then the english one, but would definitly want some i18n implementation (if not already done) so it can just detect your browser language. Also would definitly want a better translation file structure maybe just one file per language or so, because the current is very time consuming if someone wants to translate something...

[cesarmr-github]

@DaneEveritt I hear that in V2, the admin area will be rewritten in React from PHP Blade templates.
Is that true? I haven't seen it on the list.

[KingIronMan2011]

I like this idea, would probablly make everything nicer to manage.

[DaneEveritt]

We're scrapping that idea – it would be nice but the time investment is wholly just not worth it in the end right now. There are much bigger fish to fry at the moment and the admin area being rewritten to React and a new theme doesn't help us accomplish any of that.

We have some plans to bring some custom stand-alone React components into the admin area to replace very legacy raw JS, but no plans for a full rewrite right now. That got started years ago, and failed miserably.