Testing Your Integration

Run your app's test suite and production build with the default Vite preset first. Check server-rendered routes on a direct load and after client navigation, then exercise forms, portals, Suspense boundaries, and third-party components.

Disabling hydration makes hydrateRoot throw. Disabling class components also removes class error boundaries and lifecycle methods. Read the feature-flag behavior before changing presets.

Published verification#

The following evidence describes the 0.1.0 release, it is not coverage of every application or later version.

pnpm test:ci passes 1,569 tests, type checking, the built-package verifier, and all 19 source/dist size budgets. The 91 ordinary-suite skips are not passes. Native Node import order, NodeNext declarations, development/production behavior, and actual Vite feature selection are checked.

The separate Chrome gate passes 1,266 case executions across Redact and React, including repeated suites/motion modes, not 1,266 unique behaviors. Seven declared exclusions remain: six Node-only stream executions and one known React Activity hydration failure. Chrome ledger.

These are integration checks, not site-speed measurements or coverage of authenticated flows. Published-package and deployment evidence, earlier renderer controls.