-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vite #173
base: main
Are you sure you want to change the base?
Conversation
}, | ||
async argv => { | ||
const { port } = await getServeConfig(); | ||
const viteConfig = getViteConfig(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This getViteConfig
abstraction looks great. It could make it really easy to just optionally add a build.lib config object for a package
style command (similarly to how sveltekit lets you publish the lib
folder as a library
Now we'll soon have Turbopack to consider 😅 |
Heck yeah that looks great. |
Why is the internet like this and would I have it any other way? |
This is the overall tracking issue (and eventual pull request) for moving
aunty
from Webpack to Vite.aunty
's job consists of three things: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
aunty
aunty
will get two new sub-commandspackage
andpublish
which will package and publish to NPM/src/lib
directory so any components or libraries that live in that directory will be built and transpiled appropriately for release on NPMpackage.json
might be a good idea — not sure how to do this yetaunty publish
will build in any conventions we use for packages deployed to NPMaunty build
will continue to build the project as beforeserve
command will build a dev playground to use for testing and working on the library modules and thebuild
command will build the static project which could be used for documentation or implementation examples for how to use the library.