Skip to content

Conversation

@danielroe
Copy link
Member

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

this updates us to vitest v4 and drops support for previous versions of vitest.

there's still an issue with starting vitest programmatically (in the nuxt devtools) but it's unclear to me if this is a nuxt/test-utils bug or a vitest one

@danielroe danielroe marked this pull request as draft November 3, 2025 12:22
@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 3, 2025

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/test-utils@1481

commit: 2143883

@OrbisK
Copy link
Member

OrbisK commented Nov 3, 2025

There is a problem with runtime config:

  runtimeConfig: {
    public: {
      whatever: {
        hello: 'world',
      },
    },
  },

  it('renders', () => {
    const config = useRuntimeConfig()
    console.log('public', config.public)
  })
public {}

Reproduction: https://github.com/OrbisK/test-utils-fork/tree/feat/vitest-4-reprod-runtimeconfig

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