Migrate from jest to vitest

[yo-iwamoto]

Issue

#90

Overview

Migrate the test runner from jest to vitest

TODO

• migrate @kuma-ui/sheet a12258a
• migrate @kuma-ui/system 1604197
• migrate @kuma-ui/babel-plugin 6e568bc
• rm jest a1d97c2
• extract vitest config to workspace and reuse it (if needed)

Comment

• For I don't deeply understand about the implementation and the context of this issue, changes may have something wrong. If there are any oversights, please let me know.
• This task only took me around 20 minutes, so feel free to request the change.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
kuma-ui-website	❌ Failed (Inspect)			Jun 4, 2023 2:16pm

[yo-iwamoto]

only in @kuma-ui/babel-plugin, globals is set to true for babel-plugin-tester behavior.

[poteboy]

@you-5805
I appreciate your efforts on this pull request!

While trying to run the changes locally, I encountered an error with the dependency @ampproject/remapping@2.2.1 being invalid. I noticed that the lockfileVersion in pnpm-lock.yml was changed to '6.1'. Would it be possible to revert this back to '6.0' and remove the settings?

Apart from that, I noticed you mentioned 'extract vitest config to workspace and reuse it (if needed)' in your TODO list. If it's possible to centralize the vitest configuration for reuse, that would be really appreciated.

Once these changes are made, I believe your PR will be good to go. Thank you!

[yo-iwamoto]

@poteboy
Thank you for your review!

• fix lockfile version d71f683
• reuse shared config for vitest 6c32264
  I tried to define configShared as workspace module, but it seem doesn't work correctly on ESM 🤔
  So I put the vitest.shared.ts on the root like the official example.
  https://vitest.dev/guide/workspace.html#configuration

The Vercel CI seems to be failing, but I'm unable to check the details🙏
On local, pnpm i --frozen-lockfile, pnpm build, and pnpm test are passed.

[poteboy]

@you-5805
Thank you for your quick fixes!

No worries about the Vercel CI issue; it's due to an unrelated App Router cache problem that we're currently waiting on a Next.js fix for.

Everything else looks great! I appreciate your help with improving our test setup :)