chore: migrate to `@nuxt/test-utils` alpha

[danielroe]

Following the steps in https://github.com/nuxt/test-utils/issues/644, this PR migrates to the latest alpha of @nuxt/test-utils which includes nuxt-vitest.

It's primarily intended for testing any potential regressions prior to release.

Summary by CodeRabbit

• Refactor

  • Updated import paths for test configurations and utilities to align with the new project structure or dependency organization.

• Tests

  • Modified test files to use the updated import paths for the @nuxt/test-utils module.

[coderabbitai[bot]]

Walkthrough

The project has undergone a restructuring, integrating the nuxt-vitest module into the official @nuxt/test-utils. This transition involves updating import paths in configuration and test files to align with the new module locations, reflecting the shift towards an officially supported unit testing framework using Vitest in Nuxt environments.

Changes

File(s)	Change Summary
.nuxtrc, vitest.config.mjs	Updated module paths from nuxt-vitest to @nuxt/test-utils/module and test config import paths.
test/e2e.spec.ts	Changed import of url function to @nuxt/test-utils/e2e.
test/unit.spec.ts	Updated import paths for mountSuspended and NuxtTime component.

Related issues

• danielroe/nuxt-vitest#410: This issue discusses the migration of nuxt-vitest into @nuxt/test-utils, which is directly addressed by the changes in this PR as they update the import paths to the new module locations.

Poem

🐇 In the burrow of code, a change took flight,
🌟 From nuxt-vitest to @nuxt's light.
🛠️ Paths now lead to a tested dawn,
🎉 Where bugs are caught and swiftly gone.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?

---

Tips

### Chat with CodeRabbit Bot (`@coderabbitai`) - You can reply to a review comment made by CodeRabbit. - You can tag CodeRabbit on specific lines of code or files in the PR by tagging `@coderabbitai` in a comment. - You can tag `@coderabbitai` in a PR comment and ask one-off questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - The JSON schema for the configuration file is available [here](https://coderabbit.ai/integrations/coderabbit-overrides.v2.json). - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json`

[socket-security[bot]]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
vitest	0.33.0...1.0.4	None	+1/-1	1.34 MB	oreanno