feat: vitest support - #80
Open
NathanWalker wants to merge 1 commit into
Open
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Support Vitest-based unit and UI test runner, including quick start, configuration, UI testing, coverage, device networking, support matrix, and migration notes.
Can still choose Karma based options if desired (jasmine, mocha, and qunit).
ns test initprompts with all four frameworks withvitestlisted first as the recommended default, and --framework jasmine|mocha|qunit works exactly as before: same karma.conf.js template, same pinned Karma dependency set, same tests/ scaffolding. The only difference is a deprecation note in the init output pointing at vitest.ns test ios|androidroutes by detection: if the project has a vitest.config.*, it runs Vitest; otherwise it falls through to the untouched Karma server path (with a deprecation warning). So existing Karma projects keep working with zero changes, per the one-minor-cycle deprecation window you chose.