Vite

[drzax]

This is the overall tracking issue (and eventual pull request) for moving aunty from Webpack to Vite.

aunty's job consists of three things:

• project bootstrap
• dev server and final builds
• versioning and deployment

It will continue to do this things after a migration to vite. #160 has some initial notes and individual issues that require more detailed discussion will be opened and added to the vite milestone so we can have focussed discussions and keep track of decisions on issues.

Plan

• As part of the vite migration we will add packaging capabilities to aunty
  • aunty will get two new sub-commands package and publish which will package and publish to NPM
  • Packaging will target the /src/lib directory so any components or libraries that live in that directory will be built and transpiled appropriately for release on NPM
  • a separate or modified package.json might be a good idea — not sure how to do this yet
  • aunty publish will build in any conventions we use for packages deployed to NPM
• aunty build will continue to build the project as before
• This will mean that for projects that are intended to be purely libraries, the serve command will build a dev playground to use for testing and working on the library modules and the build command will build the static project which could be used for documentation or implementation examples for how to use the library.
• We need to check how the javascript entry points are generated using vite and how we'll be able to reference localhost dev versions from the CMS.
• A typescript rewrite, while desirable, is separate from the vite milestone.

[colingourlay]

Now we'll soon have Turbopack to consider 😅

[phocks]

Heck yeah that looks great.

[drzax]

Why is the internet like this and would I have it any other way?