Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
vitest-browser-react
Advanced tools
Render React components in Vitest Browser Mode. This library follows testing-library
principles and exposes only locators and utilities that encourage you to write tests that closely resemble how your React components are used.
vitest-browser-react
aims to deliver a good developer experience in Vitest Browser Mode by incorporating the locators API and retry-ability mechanism directly into the render
result. This allows you to call user methods without needing to verify the element's existence or wait for external events (like API calls) to render the element.
Requires vitest
and @vitest/browser
2.1.0 or higher.
import { render } from 'vitest-browser-react'
import { expect, test } from 'vitest'
test('counter button increments the count', async () => {
const screen = render(<Component count={1} />)
await screen.getByRole('button', { name: 'Increment' }).click()
await expect.element(screen.getByText('Count is 2')).toBeVisible()
})
💡 This library doesn't expose or use React's
act
. Instead, you should use Vitest's locators andexpect.element
API that have retry-ability mechanism baked in.
vitest-browser-react
also automatically injects render
method on the page
. Example:
// vitest.config.ts
import { defineConfig } from 'vitest/config'
export default defineConfig({
test: {
setupFiles: ['./setup-file.ts'],
browser: {
name: 'chromium',
enabled: true,
},
},
})
// ./setup-file.ts
// add an import at the top of your setup file so TypeScript can pick up types
import 'vitest-browser-react'
import { page } from '@vitest/browser/context'
test('counter button increments the count', async () => {
const screen = page.render(<Component count={1} />)
screen.cleanup()
})
Unlike @testing-library/react
, vitest-browser-react
performs cleanup of the component before the test begins, allowing you to see the rendered result in your UI. If you prefer to disable auto-cleanup, you can import the render
function from vitest-browser-react/pure
.
You can configure if the component should be rendered in Strict Mode with configure
method from vitest-browser-react/pure
:
import { configure } from 'vitest-browser-react/pure'
configure({
// disabled by default
reactStrictMode: true,
})
@testing-library/react
FAQs
Render React components in Vitest Browser Mode
We found that vitest-browser-react demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.