Skip to content

Vitest migration #1232

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

Open
wants to merge 29 commits into
base: master
Choose a base branch
from
Open

Vitest migration #1232

wants to merge 29 commits into from

Conversation

DanDroryAu
Copy link
Contributor

@DanDroryAu DanDroryAu commented Apr 14, 2025

Outline:

sku has moved to esm and is starting experimental vite support. This means that vitest makes more sense for the test suite. It allows us to test everything as esm projects and it speeds up our internal test suite. jest has also not seen a major update since 29.7 and still only has experimental esm support.

This change also helps us understand how to migrate sku projects over to vitest if they are using the sku test command.

Changes:

  • Change internal test suite to vitest.
  • Update fixture/jest-test. This test now uses the bin/jest.js file to run the tests.
  • Add port and strict-port as arguments for serve|start commands.

Copy link

changeset-bot bot commented Apr 14, 2025

🦋 Changeset detected

Latest commit: a12e61d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
sku Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@DanDroryAu DanDroryAu marked this pull request as ready for review April 14, 2025 05:04
@DanDroryAu DanDroryAu requested a review from a team as a code owner April 14, 2025 05:04
- name: Test
run: aa-exec --profile=chrome pnpm run test && aa-exec --profile=chrome pnpm run test:sku-init
run: aa-exec --profile=chrome pnpm run test
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does vitest have a cache we should persist?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked all around and there isn't any. There are some plugins that maintain a cache but they have very low usage and stars so I don't want to tie this to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants