feat: Add Vite build config

[lachlancollins]

Changes

This PR is the culmination of several attempts at making our builds work in all environments. It started in Rollup, moved to tsup, and is now settling on Vite with plugins. This export contains all the generic settings which all our packages would need.

Limitations

• Unlike the current tsup setup on some repos (e.g. query), it does not generate "legacy" builds for older bundlers (looking at you, Webpack 4). Migrating to this config here would be a major release.
• While it can compile Svelte and Angular code, these frameworks have their own incredible build tools which should be used instead.

Todo

• Integration tests
• Documentation

[crutchcorn]

FWIW the Angular Vite story is pretty good:

https://github.com/analogjs/analog/tree/main/packages/vite-plugin-angular

It's maintained by the Analog team, who use it for their metaframework and utilizes the official build tools under the hood.

[crutchcorn]

Also, and apologies for potentially missing this - what is a "legacy" build. Specifically what changes are there over CJS?

[lachlancollins]

FWIW the Angular Vite story is pretty good:

analogjs/analog@main/packages/vite-plugin-angular

It's maintained by the Analog team, who use it for their metaframework and utilizes the official build tools under the hood.

The angular-query-experimental package uses ng-packagr, which I think uses that plugin!

[lachlancollins]

Also, and apologies for potentially missing this - what is a "legacy" build. Specifically what changes are there over CJS?

Legacy transpiled for bundlers that supported lower than ES2020, and therefore were larger files.

[crutchcorn]

@lachlancollins could we have two Vite config files and pass this as a plugin to one in order to solve this?

https://www.npmjs.com/package/@vitejs/plugin-legacy

[crutchcorn]

I know it seems hacky/silly to run multiple instances of Vite for different outputs, but isn't that what tsup effectively does as well?

[lachlancollins]

I know it seems hacky/silly to run multiple instances of Vite for different outputs, but isn't that what tsup effectively does as well?

Oh for sure, I'm just wondering if we should be supporting deprecated bundlers which hold back the ecosystem. Introducing this to something like query would be a major release anyway, so it would be a reasonable time to drop Webpack v4.

[crutchcorn]

Fair enough! You've got my vote.