Migrate project to Vite for asset bundling

vivgui commented 2 years ago

The project currently uses webpack for assets bundling but there's an interest in switching to Vite. This PR attempts to do that migration. I first tested this on the foundation theme (you can see my repo fork here) and things worked correctly.

One major thing that the migration to Vite changed is that Vite doesn't use .browserslistrc for setting browser compatibility, it uses esbuild instead so the .config/.browserslistrc file is not needed.

Besides that, I tried my best to replace all the webpack-specific functionality using Vite plugins and configurations.

I know this is a significant change and I'm open to discussing how to best approach it. I just wanted to demonstrate that migrating to Vite is possible and worthwhile.

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[x] Yes
[ ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

[x] It's submitted to the dev branch, not the main branch

If adding a new feature, the PR's description includes:

[x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information: