chore: migrate to vite and vitest #200
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
henningmu
reviewed
Nov 4, 2025
Collaborator
henningmu
left a comment
henningmu
left a comment
There was a problem hiding this comment.
Changes look good, let's ship this once CI is no longer complaining 👍
Contributor
|
No objections from me. |
Member
|
✅ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrates build and tests to vite. The motivation is to make it a bit easier to support React and JSX in a future where we need something for MCP-UI or ChatGPT apps. We may also make use of vite's importing assets as strings for HTML or CSS templates.
Most of the changes are in the tests, that change a bit from jest to vitest.