TASK ID: @tanstack/vue-router:test:types $ pnpm run test:unit .test-d.ts $ vitest .test-d.ts 6:43:28 PM [vite] warning: `esbuild` option was specified by "vite:vue-jsx" plugin. This option is deprecated, please use `oxc` instead. The plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the resolve.tsconfigPaths option. You can remove the plugin and set resolve.tsconfigPaths: true in your Vite config instead. Both esbuild and oxc options were set. oxc options will be used and esbuild options will be ignored. The following esbuild options were set: `{ include: /\.ts$/ }` Testing types with tsc and vue-tsc is an experimental feature. Breaking changes might not follow SemVer, please pin Vitest's version when using it. RUN v4.1.4 /home/workflows/workspace/packages/vue-router ✓ @tanstack/vue-router TS tests/link.test-d.tsx (30 tests) ✓ @tanstack/vue-router TS tests/route.test-d.tsx (42 tests) ✓ @tanstack/vue-router TS tests/useSearch.test-d.tsx (11 tests) ✓ @tanstack/vue-router TS tests/useLoaderData.test-d.tsx (5 tests) ✓ @tanstack/vue-router TS tests/useRouteContext.test-d.tsx (4 tests) ✓ @tanstack/vue-router TS tests/useParams.test-d.tsx (5 tests) ✓ @tanstack/vue-router TS tests/router.test-d.tsx (8 tests) ✓ @tanstack/vue-router TS tests/Matches.test-d.tsx (5 tests) ✓ @tanstack/vue-router TS tests/fileRoute.test-d.tsx (5 tests) ✓ @tanstack/vue-router TS tests/routeApi.test-d.tsx (8 tests) ✓ @tanstack/vue-router TS tests/useBlocker.test-d.tsx (3 tests) ✓ @tanstack/vue-router TS tests/useMatch.test-d.tsx (4 tests) ✓ @tanstack/vue-router TS tests/useNavigate.test-d.tsx (3 tests) ✓ @tanstack/vue-router TS tests/useRouterState.test-d.tsx (1 test) ✓ @tanstack/vue-router TS tests/useLocation.test-d.tsx (2 tests) ✓ @tanstack/vue-router TS tests/RouterProvider.test-d.tsx (1 test) ✓ @tanstack/vue-router TS tests/redirects.test-d.tsx (1 test) ⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯ Vitest caught 1 unhandled error during the test run. This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected. ⎯⎯⎯ Unhandled Source Error ⎯⎯⎯ TypeCheckError: Object literal may only specify known properties, and 'foo' does not exist in type 'Partial> | "root"[]'. ❯ tests/link.test.tsx:5937:31 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Test Files 17 passed (17) Tests 138 passed (138) Type Errors no errors Errors 1 error Start at 18:43:29 Duration 32.77s (transform 0ms, setup 0ms, import 0ms, tests 0ms, environment 0ms, typecheck 30.86s) [ELIFECYCLE] Command failed with exit code 1. [ELIFECYCLE] Command failed with exit code 1. TASK ID: @tanstack/react-router:test:unit $ vitest 6:43:22 PM [vite] warning: `esbuild` option was specified by "vite:react-babel" plugin. This option is deprecated, please use `oxc` instead. 6:43:22 PM [vite] warning: `optimizeDeps.esbuildOptions` option was specified by "vite:react-babel" plugin. This option is deprecated, please use `optimizeDeps.rolldownOptions` instead. The plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the resolve.tsconfigPaths option. You can remove the plugin and set resolve.tsconfigPaths: true in your Vite config instead. Both esbuild and oxc options were set. oxc options will be used and esbuild options will be ignored. The following esbuild options were set: `{ jsx: 'automatic', jsxImportSource: undefined }` Testing types with tsc and vue-tsc is an experimental feature. Breaking changes might not follow SemVer, please pin Vitest's version when using it. RUN v4.1.4 /home/workflows/workspace/packages/react-router stderr | tests/router.test.tsx > invalidate > does not render the route component while async loader notFound is waiting for later matches to settle Warning: A notFoundError was encountered on the route with ID "/parent/child", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > does not throw an error when the search param is valid Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > throws an error when the search param is not valid SearchParamError: [ { "expected": "string", "code": "invalid_type", "path": [ "search" ], "message": "Invalid input: expected string, received undefined" } ] at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3057:13) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1484:13) ... 6 lines matching cause stack trace ... at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 at new Promise () { [stack]: [Getter/Setter], [message]: '[\n' + ' {\n' + ' "expected": "string",\n' + ' "code": "invalid_type",\n' + ' "path": [\n' + ' "search"\n' + ' ],\n' + ' "message": "Invalid input: expected string, received undefined"\n' + ' }\n' + ']', [cause]: TestValidationError: validation failed at Object.validate (/home/workflows/workspace/packages/react-router/tests/router.test.tsx:1830:20) at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3051:48) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1484:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1410:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2422:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2452:16 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'validation failed', name: 'TestValidationError', issues: [ { expected: 'string', code: 'invalid_type', path: [ 'search', [length]: 1 ], message: 'Invalid input: expected string, received undefined' }, [length]: 1 ] } } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: __root__/ stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > does not throw an error when the search param is valid Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > throws an error when the search param is not valid SearchParamError: validation failed at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1496:32) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1410:17) ... 5 lines matching cause stack trace ... at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 at new Promise () at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2449:19) { [stack]: [Getter/Setter], [message]: 'validation failed', [cause]: TestValidationError: validation failed at Object.parse (/home/workflows/workspace/packages/react-router/tests/router.test.tsx:1845:19) at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3065:27) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1484:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1410:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2422:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2452:16 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'validation failed', name: 'TestValidationError', issues: [ { message: 'search must be a string' }, [length]: 1 ] } } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: __root__/ stderr | tests/router.test.tsx > does not strip search params if search validation fails > root is missing SearchParamError: [ { "expected": "string", "code": "invalid_type", "path": [ "root" ], "message": "Invalid input: expected string, received undefined" } ] at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3057:13) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1484:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1410:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2422:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2452:16 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 at new Promise () { [stack]: [Getter/Setter], [message]: '[\n' + ' {\n' + ' "expected": "string",\n' + ' "code": "invalid_type",\n' + ' "path": [\n' + ' "root"\n' + ' ],\n' + ' "message": "Invalid input: expected string, received undefined"\n' + ' }\n' + ']', [cause]: { issues: [ { expected: 'string', code: 'invalid_type', path: [ 'root', [length]: 1 ], message: 'Invalid input: expected string, received undefined' }, [length]: 1 ] } } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: [ { "expected": "string", "code": "invalid_type", "path": [ "root" ], "message": "Invalid input: expected string, received undefined" } ] stderr | tests/router.test.tsx > does not strip search params if search validation fails > index is missing SearchParamError: [ { "expected": "string", "code": "invalid_type", "path": [ "index" ], "message": "Invalid input: expected string, received undefined" } ] at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3057:13) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1484:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1410:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2422:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2452:16 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 at new Promise () { [stack]: [Getter/Setter], [message]: '[\n' + ' {\n' + ' "expected": "string",\n' + ' "code": "invalid_type",\n' + ' "path": [\n' + ' "index"\n' + ' ],\n' + ' "message": "Invalid input: expected string, received undefined"\n' + ' }\n' + ']', [cause]: { issues: [ { expected: 'string', code: 'invalid_type', path: [ 'index', [length]: 1 ], message: 'Invalid input: expected string, received undefined' }, [length]: 1 ] } } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: [ { "expected": "string", "code": "invalid_type", "path": [ "index" ], "message": "Invalid input: expected string, received undefined" } ] stderr | tests/router.test.tsx > statusCode > should reset statusCode to 200 when navigating from 404 to valid route Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > statusCode > should reset statusCode to 200 when navigating from 404 to valid route Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > statusCode > status code is set when loader/beforeLoad throws (isAsync=true) > should set statusCode to 500 when a route loader throws an Error Error: test-error at /home/workflows/workspace/packages/react-router/tests/router.test.tsx:2260:15 at /home/workflows/workspace/packages/react-router/tests/router.test.tsx:2252:13 at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'test-error' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /loader-throws-error/loader-throws-error stderr | tests/router.test.tsx > statusCode > status code is set when loader/beforeLoad throws (isAsync=true) > should set statusCode to 500 when a route beforeLoad throws an Error Error: test-error at /home/workflows/workspace/packages/react-router/tests/router.test.tsx:2260:15 at Object.beforeLoad (/home/workflows/workspace/packages/react-router/tests/router.test.tsx:2252:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'test-error' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /beforeload-throws-error/beforeload-throws-error stderr | tests/router.test.tsx > statusCode > status code is set when loader/beforeLoad throws (isAsync=false) > should set statusCode to 500 when a route loader throws an Error Error: test-error at /home/workflows/workspace/packages/react-router/tests/router.test.tsx:2260:15 at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'test-error' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /loader-throws-error/loader-throws-error stderr | tests/router.test.tsx > statusCode > status code is set when loader/beforeLoad throws (isAsync=false) > should set statusCode to 500 when a route beforeLoad throws an Error Error: test-error at Object.beforeLoad (/home/workflows/workspace/packages/react-router/tests/router.test.tsx:2260:15) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'test-error' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /beforeload-throws-error/beforeload-throws-error stderr | tests/router.test.tsx > Router rewrite functionality > should handle subdomain to path rewriting with input An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/router.test.tsx > Router rewrite functionality > should handle output rewrite when navigating An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act ✓ @tanstack/react-router tests/router.test.tsx (187 tests) 2747ms stderr | tests/link.test.tsx > Link > when the current route is the root with beforeLoad that throws Error: Something went wrong! at Object.beforeLoad (/home/workflows/workspace/packages/react-router/tests/link.test.tsx:962:15) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'Something went wrong!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: __root__/ stderr | tests/link.test.tsx > Link > when navigating to /posts with invalid search SearchParamError: Not a number! at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1496:32) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1410:17) ... 5 lines matching cause stack trace ... at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 at new Promise () at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2449:19) { [stack]: [Getter/Setter], [message]: 'Not a number!', [cause]: Error: Not a number! at validateSearch (/home/workflows/workspace/packages/react-router/tests/link.test.tsx:1456:32) at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3069:12) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1484:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1410:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2422:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2452:16 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'Not a number!' } } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /posts/posts stderr | tests/link.test.tsx > Link > when navigating to /posts with a loader An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/link.test.tsx > Link > when navigating to /posts with a loader that errors An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/link.test.tsx > Link > when navigating to /posts with a loader that errors Error: at loader (/home/workflows/workspace/packages/react-router/tests/link.test.tsx:1596:15) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter] } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /posts/posts{"page":{"page":2}} stderr | tests/link.test.tsx > Link > when navigating away from a route with a loader that errors An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/link.test.tsx > Link > when navigating away from a route with a loader that errors Error: Something went wrong! at /home/workflows/workspace/packages/react-router/tests/link.test.tsx:1648:19 at file:///home/workflows/workspace/node_modules/.pnpm/@vitest+runner@4.1.4/node_modules/@vitest/runner/dist/chunk-artifact.js:302:11 at file:///home/workflows/workspace/node_modules/.pnpm/@vitest+runner@4.1.4/node_modules/@vitest/runner/dist/chunk-artifact.js:1903:26 at file:///home/workflows/workspace/node_modules/.pnpm/@vitest+runner@4.1.4/node_modules/@vitest/runner/dist/chunk-artifact.js:2326:20 at new Promise () at runWithCancel (file:///home/workflows/workspace/node_modules/.pnpm/@vitest+runner@4.1.4/node_modules/@vitest/runner/dist/chunk-artifact.js:2323:10) at file:///home/workflows/workspace/node_modules/.pnpm/@vitest+runner@4.1.4/node_modules/@vitest/runner/dist/chunk-artifact.js:2305:20 at new Promise () at runWithTimeout (file:///home/workflows/workspace/node_modules/.pnpm/@vitest+runner@4.1.4/node_modules/@vitest/runner/dist/chunk-artifact.js:2272:10) at file:///home/workflows/workspace/node_modules/.pnpm/@vitest+runner@4.1.4/node_modules/@vitest/runner/dist/chunk-artifact.js:2955:64 { [stack]: [Getter/Setter], [message]: 'Something went wrong!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /posts/posts{"page":{}} stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that redirects An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that throws an error Error: Oops. Something went wrong! at Object.beforeLoad (/home/workflows/workspace/packages/react-router/tests/link.test.tsx:1824:15) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'Oops. Something went wrong!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /posts/posts stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that throws an error bubbles to the root Error: Oops. Something went wrong! at Object.beforeLoad (/home/workflows/workspace/packages/react-router/tests/link.test.tsx:1875:15) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'Oops. Something went wrong!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: __root__/ stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that throws an error bubbles to the nearest parent Error: Oops. Something went wrong! at Object.beforeLoad (/home/workflows/workspace/packages/react-router/tests/link.test.tsx:1936:15) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'Oops. Something went wrong!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /posts/posts stderr | tests/link.test.tsx > Link > when navigating to the root with an error in component Error: Error from component should not render notFoundComponent at component (/home/workflows/workspace/packages/react-router/tests/link.test.tsx:1971:15) at Object.react_stack_bottom_frame (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:25904:20) at renderWithHooks (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:7662:22) at updateFunctionComponent (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:10166:19) at beginWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:11778:18) at runWithFiberInDEV (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:874:13) at performUnitOfWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17641:22) at workLoopSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17469:41) at renderRootSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17450:11) at performWorkOnRoot (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:16583:35) { [stack]: [Getter/Setter], [message]: 'Error from component should not render notFoundComponent' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: __root__/ stderr | tests/link.test.tsx > Link > when navigating from /invoices to ./invoiceId and the current route is /posts/$postId/details Could not find match for from: /invoices stderr | tests/link.test.tsx > Link > when navigating from /invoices to ./invoiceId and the current route is /posts/$postId/details An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/link.test.tsx > Link > when navigating to /post/$postId with a redirect from /post/$postId to ../../login in beforeLoad An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act Error: Not implemented: navigation (except hash changes) at module.exports (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/browser/not-implemented.js:9:17) at navigateFetch (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/window/navigation.js:77:3) at exports.navigate (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/window/navigation.js:55:3) at Timeout._onTimeout (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/nodes/HTMLHyperlinkElementUtils-impl.js:81:7) at listOnTimeout (node:internal/timers:608:17) at processTimers (node:internal/timers:543:7) undefined Error: Not implemented: navigation (except hash changes) at module.exports (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/browser/not-implemented.js:9:17) at navigateFetch (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/window/navigation.js:77:3) at exports.navigate (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/window/navigation.js:55:3) at Timeout._onTimeout (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/nodes/HTMLHyperlinkElementUtils-impl.js:81:7) at listOnTimeout (node:internal/timers:608:17) at processTimers (node:internal/timers:543:7) undefined stderr | tests/link.test.tsx > createLink > should pass activeProps and inactiveProps to the custom link React does not recognize the `overrideMeIfYouWant` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `overridemeifyouwant` instead. If you accidentally passed it from a parent component, remove it from the DOM element. stderr | tests/link.test.tsx > relative links with { basepath: '' } > should navigate to a child link based on pathname Warning: A notFoundError was encountered on the route with ID "/param/$param/a", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) Warning: A notFoundError was encountered on the route with ID "/param/$param/a", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/link.test.tsx > relative links with { basepath: '/basepath' } > should navigate to a child link based on pathname Warning: A notFoundError was encountered on the route with ID "/param/$param/a", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) ✓ @tanstack/react-router tests/link.test.tsx (131 tests) 8507ms ✓ when using renderHook it returns a hook with same content to prove rerender works 303ms ✓ when a Link is disabled 1111ms ✓ updates exact and fuzzy active state before the next route renders 570ms ✓ updates exact active state and href when only params change with params=true 527ms ✓ updates search-sensitive active state immediately with and without search=true 526ms ✓ when navigating away from a route with a loader that errors 1038ms ✓ Router.preload="intent", pendingComponent renders during unresolved route loader 716ms ✓ should respect target attribute set by custom component 1011ms stderr | tests/useNavigate.test.tsx > when navigating from /invoices to ./invoiceId and the current route is /posts/$postId/details An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > should navigate to current route with search params when using "." in nested route structure from Index Route An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > should navigate to current route with search params when using "." in nested route structure from Index Route An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > should navigate to current route with search params when using "." in nested route structure from non-Index Route An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to DetailComponent inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to DetailComponent inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > should navigate to current route with search params when using "." in nested route structure from non-Index Route An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to DetailComponent inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to DetailComponent inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '' } > should navigate to the parent route An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '' } > should navigate to the parent route and keep params An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '' } > should navigate to the parent route and change params An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '' } > should navigate to a relative link based on render location with basepath An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '' } > should navigate to a parent link based on render location An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '' } > should navigate to a parent link based on active location An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '' } > should navigate to same route with different params An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '/basepath' } > should navigate to the parent route An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '/basepath' } > should navigate to the parent route and keep params An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '/basepath' } > should navigate to the parent route and change params An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '/basepath' } > should navigate to a relative link based on render location with basepath An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '/basepath' } > should navigate to a parent link based on render location An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '/basepath' } > should navigate to a parent link based on active location An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useNavigate.test.tsx > relative useNavigate with { basepath: '/basepath' } > should navigate to same route with different params An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act ✓ @tanstack/react-router tests/useNavigate.test.tsx (46 tests) 1045ms ✓ @tanstack/react-router tests/navigate.test.tsx (56 tests) 107ms ✓ @tanstack/react-router tests/optional-path-params.test.tsx (29 tests) 531ms hello empty type ✓ @tanstack/react-router tests/Scripts.test.tsx (19 tests) 607ms stdout | tests/loaders.test.tsx > reproducer for #2031 beforeload called beforeload called stdout | tests/loaders.test.tsx > reproducer for #2053 beforeload called stderr | tests/loaders.test.tsx > reproducer for #2198 - throw error from beforeLoad upon initial load Error: Test! at Object.beforeLoad (/home/workflows/workspace/packages/react-router/tests/loaders.test.tsx:253:13) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'Test!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/loaders.test.tsx > throw error from loader upon initial load Error: Test! at loader (/home/workflows/workspace/packages/react-router/tests/loaders.test.tsx:281:13) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'Test!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/loaders.test.tsx > throw error from beforeLoad when navigating to route Error: Test! at Object.beforeLoad (/home/workflows/workspace/packages/react-router/tests/loaders.test.tsx:320:13) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'Test!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /foo/foo ✓ @tanstack/react-router tests/routeContext.test.tsx (77 tests | 1 skipped) 14217ms ✓ modified route context, present in the index route 306ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in the beforeLoad of the index route 312ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in the loader of the index route 311ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the beforeLoad of the /about route 320ms �� on navigate, route context is present in the /person route after a redirect is thrown in the loader of the /about route 319ms ✓ nested destination on navigate, route context in the /nested/about route is correctly inherited from the /nested parent 318ms ✓ nested destination on navigate, when a redirect is thrown in beforeLoad in /about, the /nested/person route context is correctly inherited from its parent /nested 468ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from parent /nested 471ms ✓ _layout on first-load, route context in the index route is correctly inherited from the layout parent 308ms ✓ _layout on navigate, route context in the /about route is correctly inherited from the layout parent 314ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 466ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 468ms ✓ modified route context, present in the index route 307ms ✓ on navigate (with preload), loader isn't invoked with undefined context if beforeLoad is pending when navigation happens 317ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in beforeLoad of the index route 307ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in loader of the index route 310ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the beforeLoad of the /about route 317ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the loader of the /about route 320ms ✓ nested destination on navigate, route context in the /nested/about route is correctly inherited from the /nested parent 320ms ✓ nested destination on navigate, when a redirect is thrown in beforeLoad in /about, the /nested/person route context is correctly inherited from its parent /nested 483ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from parent /nested 467ms ✓ _layout on first-load, route context in the index route is correctly inherited from the layout parent 306ms ✓ _layout on navigate, route context in the /about route is correctly inherited from the layout parent 315ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 472ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 490ms ✓ route context, (sleep in beforeLoad), with immediate navigation 309ms ✓ nested destination on navigate, when a redirect is thrown in beforeLoad in /about, the /nested/person route context is correctly inherited from its parent /nested 334ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from its parent /nested 400ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 315ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 319ms stderr | tests/loaders.test.tsx > cancelMatches after pending timeout Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/route.test.tsx > route.head > meta is set when loader throws notFound Warning: A notFoundError was encountered on the route with ID "/", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/route.test.tsx > route.head > meta is set when loader throws an error Error: Fly, you fools! at loader (/home/workflows/workspace/packages/react-router/tests/route.test.tsx:343:15) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'Fly, you fools!' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: Fly, you fools! stderr | tests/loaders.test.tsx > cancelMatches after pending timeout An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act ✓ @tanstack/react-router tests/route.test.tsx (26 tests) 1303ms ✓ @tanstack/react-router tests/loaders.test.tsx (14 tests) 5807ms ✓ reproducer #4245 592ms ✓ clears pendingTimeout when match resolves 565ms ✓ cancelMatches after pending timeout 3084ms ✓ reproducer for #6388 - rapid navigation between parameterized routes should not trigger errorComponent 534ms stderr | tests/useBlocker.test.tsx > useBlocker > should allow navigation from 404 page when blocker is active An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useBlocker.test.tsx > useBlocker > should allow navigation from 404 page when blocker is active An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useBlocker.test.tsx > useBlocker > should handle blocker navigation from 404 to another 404 An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useBlocker.test.tsx > useBlocker > should handle blocker navigation from 404 to another 404 An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act ✓ @tanstack/react-router tests/useBlocker.test.tsx (9 tests) 287ms stderr | tests/not-found.test.tsx > correct notFoundComponent is rendered for mode={ notFoundMode: 'fuzzy', expectedNotFoundComponent: 'settings-not-found' } An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > correct notFoundComponent is rendered for mode={ notFoundMode: 'fuzzy', expectedNotFoundComponent: 'settings-not-found' } An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on navigate in the route 'beforeLoad' function Error: error thrown at Object.asyncToThrowFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/not-found.test.tsx > correct notFoundComponent is rendered for mode={ notFoundMode: 'fuzzy', expectedNotFoundComponent: 'settings-not-found' } An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > correct notFoundComponent is rendered for mode={ notFoundMode: 'fuzzy', expectedNotFoundComponent: 'settings-not-found' } An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > correct notFoundComponent is rendered for mode={ notFoundMode: 'root', expectedNotFoundComponent: 'root-not-found' } An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > correct notFoundComponent is rendered for mode={ notFoundMode: 'root', expectedNotFoundComponent: 'root-not-found' } An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > correct notFoundComponent is rendered for mode={ notFoundMode: 'root', expectedNotFoundComponent: 'root-not-found' } An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > correct notFoundComponent is rendered for mode={ notFoundMode: 'root', expectedNotFoundComponent: 'root-not-found' } An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > defaultNotFoundComponent and notFoundComponent receives data props via spread operator An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > defaultNotFoundComponent and notFoundComponent receives data props via spread operator An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > defaultNotFoundComponent and notFoundComponent receives data props via spread operator An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > defaultNotFoundComponent and notFoundComponent receives data props via spread operator An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > component-thrown bare notFound renders current route notFoundComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > component-thrown bare notFound renders current route notFoundComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act { isNotFound: true, routeId: '/parent/child' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act { isNotFound: true, routeId: '/parent/child' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. stderr | tests/not-found.test.tsx > component-thrown bare notFound falls back to nearest ancestor notFoundComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > component-thrown bare notFound falls back to nearest ancestor notFoundComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act { isNotFound: true, routeId: '/parent' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act { isNotFound: true, routeId: '/parent' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. stderr | tests/not-found.test.tsx > beforeLoad notFound with routeId targets root notFoundComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > beforeLoad notFound with routeId targets root notFoundComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > beforeLoad notFound with routeId targets parent boundary and preserves parent loader data An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > beforeLoad notFound with routeId targets parent boundary and preserves parent loader data An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act Warning: A notFoundError was encountered on the route with ID "/parent/child", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to OutletImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchInnerImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > beforeLoad notFound with routeId targets parent boundary and preserves parent loader data An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > beforeLoad notFound with non-exact routeId falls back to root notFoundComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/not-found.test.tsx > beforeLoad notFound with non-exact routeId falls back to root notFoundComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchImpl inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act ✓ @tanstack/react-router tests/not-found.test.tsx (8 tests) 341ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on navigate in the route 'loader' function Error: error thrown at asyncToThrowFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about ✓ @tanstack/react-router tests/redirect.test.tsx (6 tests) 1314ms ✓ when `redirect` is thrown in `beforeLoad` 306ms ✓ when root `beforeLoad` redirects while root pendingComponent is showing and the target route is lazy 555ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on first load in the route 'beforeLoad' function Error: error thrown at Object.asyncToThrowFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on first load in the route 'loader' function Error: error thrown at asyncToThrowFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/Matches.test.tsx > should show pendingComponent of root route React does not recognize the `data-testId` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `data-testid` instead. If you accidentally passed it from a parent component, remove it from the DOM element. stderr | tests/Matches.test.tsx > matching on different param types > 'param with braces' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'param without braces' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'param with prefix' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'param with suffix' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'param with prefix and suffix' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'wildcard with no braces' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'wildcard with braces' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'wildcard with prefix' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'wildcard with suffix' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'optional param with no prefix/suffix …' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/Matches.test.tsx > matching on different param types > 'optional param with required param, p…' Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on navigate in the route 'beforeLoad' function Error: error thrown at Object.throwFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about ✓ @tanstack/react-router tests/Matches.test.tsx (24 tests) 1221ms ✓ should show pendingComponent of root route 510ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on navigate in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/useParams.test.tsx > useParams({ strict: false }) returns parsed params after child navigation An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useParams.test.tsx > useParams({ strict: false }) returns parsed params after child navigation Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/useParams.test.tsx > useParams({ strict: false }) returns parsed params after child navigation An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/useParams.test.tsx > useParams({ strict: false }) returns parsed params after child navigation Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) ✓ @tanstack/react-router tests/useParams.test.tsx (2 tests) 348ms ✓ useParams must return parsed result if applicable. 317ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Error: error thrown at Object.throwFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on first load in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > async loader, async beforeLoad, pendingMs An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > redirection in preload An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > redirection in preload An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > redirection in preload An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > redirection in preload An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > sync beforeLoad An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > nothing An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > not found in beforeLoad An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to CatchNotFound inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > hover preload, then navigate, w/ async loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > hover preload, then navigate, w/ async loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > hover preload, then navigate, w/ async loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > hover preload, then navigate, w/ async loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > navigate, w/ preloaded & async loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > navigate, w/ preloaded & async loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on navigate in the route 'beforeLoad' function Error: error thrown at Object.asyncToThrowFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > navigate, w/ preloaded & async loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > navigate, w/ preloaded & async loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > navigate, w/ preloaded & sync loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > navigate, w/ preloaded & sync loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > navigate, w/ preloaded & sync loaders An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > navigate, w/ previous navigation & async loader An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to ForwardRef inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > preload a preloaded route w/ async loader An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > preload a preloaded route w/ async loader An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to MatchesInner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > preload a preloaded route w/ async loader An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > preload a preloaded route w/ async loader An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > preload a preloaded route w/ async loader An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act ✓ @tanstack/react-router tests/store-updates-during-navigation.test.tsx (10 tests) 1902ms ✓ async loader, async beforeLoad, pendingMs 684ms ✓ sync beforeLoad 467ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on navigate in the route 'loader' function Error: error thrown at asyncToThrowFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/renderRouterToStream.test.tsx > renderRouterToStream - pipeable sync errors > request abort aborts pipeable and errors body Error reading appStream: Error: request-gone at /home/workflows/workspace/packages/react-router/tests/renderRouterToStream.test.tsx:223:24 at processTicksAndRejections (node:internal/process/task_queues:105:5) at file:///home/workflows/workspace/node_modules/.pnpm/@vitest+runner@4.1.4/node_modules/@vitest/runner/dist/chunk-artifact.js:1903:20 ✓ @tanstack/react-router tests/renderRouterToStream.test.tsx (6 tests) 53ms ✓ @tanstack/react-router tests/searchMiddleware.test.tsx (5 tests) 191ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on first load in the route 'beforeLoad' function Error: error thrown at Object.asyncToThrowFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on first load in the route 'loader' function Error: error thrown at asyncToThrowFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on navigate in the route 'beforeLoad' function Error: error thrown at Object.throwFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on navigate in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Error: error thrown at Object.throwFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // ✓ @tanstack/react-router tests/blocker.test.tsx (13 tests) 4395ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'postsLink' 1020ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'postsLink' 1014ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'button' 1016ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'button' 1013ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on first load in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > stale route errors do not leak after navigation > navigating away from a 'loader' error does not call the next route errorComponent Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > stale route errors do not leak after navigation > navigating away from a 'render' error does not call the next route errorComponent Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at RenderErrorComponent (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:193:15) at Object.react_stack_bottom_frame (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:25904:20) at renderWithHooks (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:7662:22) at updateFunctionComponent (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:10166:19) at beginWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:11778:18) at runWithFiberInDEV (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:874:13) at performUnitOfWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17641:22) at workLoopSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17469:41) at renderRootSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17450:11) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on navigate in the route 'beforeLoad' function Error: error thrown at Object.asyncToThrowFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/createLazyRoute.test.tsx > preload: matched routes > should render a lazy route errorComponent when the loader throws on first load Error: lazy error at loader (/home/workflows/workspace/packages/react-router/tests/createLazyRoute.test.tsx:112:15) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'lazy error' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /lazy-error/lazy-error ✓ @tanstack/react-router tests/createLazyRoute.test.tsx (3 tests) 2633ms ✓ should wait for lazy options to be streamed in before 2526ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on navigate in the route 'loader' function Error: error thrown at asyncToThrowFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/useMatch.test.tsx > useMatch > when match is not found > throws if shouldThrow = undefined Error: Invariant failed: Could not find an active match from "/posts" at /home/workflows/workspace/packages/react-router/src/useMatch.tsx:149:15 at memoizedSelector (/home/workflows/workspace/node_modules/.pnpm/use-sync-external-store@1.6.0_react@19.2.3/node_modules/use-sync-external-store/cjs/use-sync-external-store-shim/with-selector.development.js:47:30) at /home/workflows/workspace/node_modules/.pnpm/use-sync-external-store@1.6.0_react@19.2.3/node_modules/use-sync-external-store/cjs/use-sync-external-store-shim/with-selector.development.js:71:22 at mountSyncExternalStore (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:8125:24) at Object.useSyncExternalStore (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:26269:16) at process.env.NODE_ENV.exports.useSyncExternalStore (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1270:34) at process.env.NODE_ENV.exports.useSyncExternalStoreWithSelector (/home/workflows/workspace/node_modules/.pnpm/use-sync-external-store@1.6.0_react@19.2.3/node_modules/use-sync-external-store/cjs/use-sync-external-store-shim/with-selector.development.js:82:19) at useStore (file:///home/workflows/workspace/node_modules/.pnpm/@tanstack+react-store@0.9.3_react-dom@19.2.3_react@19.2.3__react@19.2.3/node_modules/@tanstack/react-store/dist/esm/useStore.js:19:28) at useMatch (/home/workflows/workspace/packages/react-router/src/useMatch.tsx:146:10) at RootComponent (/home/workflows/workspace/packages/react-router/tests/useMatch.test.tsx:84:11) { [stack]: [Getter/Setter], [message]: 'Invariant failed: Could not find an active match from "/posts"' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: Invariant failed: Could not find an active match from "/posts" stderr | tests/useMatch.test.tsx > useMatch > when match is not found > throws if shouldThrow = true Error: Invariant failed: Could not find an active match from "/posts" at /home/workflows/workspace/packages/react-router/src/useMatch.tsx:149:15 at memoizedSelector (/home/workflows/workspace/node_modules/.pnpm/use-sync-external-store@1.6.0_react@19.2.3/node_modules/use-sync-external-store/cjs/use-sync-external-store-shim/with-selector.development.js:47:30) at /home/workflows/workspace/node_modules/.pnpm/use-sync-external-store@1.6.0_react@19.2.3/node_modules/use-sync-external-store/cjs/use-sync-external-store-shim/with-selector.development.js:71:22 at mountSyncExternalStore (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:8125:24) at Object.useSyncExternalStore (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:26269:16) at process.env.NODE_ENV.exports.useSyncExternalStore (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1270:34) at process.env.NODE_ENV.exports.useSyncExternalStoreWithSelector (/home/workflows/workspace/node_modules/.pnpm/use-sync-external-store@1.6.0_react@19.2.3/node_modules/use-sync-external-store/cjs/use-sync-external-store-shim/with-selector.development.js:82:19) at useStore (file:///home/workflows/workspace/node_modules/.pnpm/@tanstack+react-store@0.9.3_react-dom@19.2.3_react@19.2.3__react@19.2.3/node_modules/@tanstack/react-store/dist/esm/useStore.js:19:28) at useMatch (/home/workflows/workspace/packages/react-router/src/useMatch.tsx:146:10) at RootComponent (/home/workflows/workspace/packages/react-router/tests/useMatch.test.tsx:84:11) { [stack]: [Getter/Setter], [message]: 'Invariant failed: Could not find an active match from "/posts"' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: Invariant failed: Could not find an active match from "/posts" ✓ @tanstack/react-router tests/useMatch.test.tsx (7 tests) 158ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on first load in the route 'beforeLoad' function Error: error thrown at Object.asyncToThrowFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // ✓ @tanstack/react-router tests/ClientOnly.test.tsx (3 tests) 100ms stderr | tests/disableGlobalCatchBoundary.test.tsx > disableGlobalCatchBoundary option > catches errors in global boundary when disableGlobalCatchBoundary is false Error: Test error at ThrowingComponent (/home/workflows/workspace/packages/react-router/tests/disableGlobalCatchBoundary.test.tsx:16:9) at Object.react_stack_bottom_frame (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:25904:20) at renderWithHooks (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:7662:22) at updateFunctionComponent (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:10166:19) at beginWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:11778:18) at runWithFiberInDEV (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:874:13) at performUnitOfWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17641:22) at workLoopSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17469:41) at renderRootSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17450:11) at performWorkOnRoot (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:16583:35) { [stack]: [Getter/Setter], [message]: 'Test error' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: Test error stderr | tests/disableGlobalCatchBoundary.test.tsx > disableGlobalCatchBoundary option > errors bubble up to external error boundary when disableGlobalCatchBoundary is true Error: Test error at ThrowingComponent (/home/workflows/workspace/packages/react-router/tests/disableGlobalCatchBoundary.test.tsx:16:9) at Object.react_stack_bottom_frame (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:25904:20) at renderWithHooks (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:7662:22) at updateFunctionComponent (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:10166:19) at beginWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:11778:18) at runWithFiberInDEV (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:874:13) at performUnitOfWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17641:22) at workLoopSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17469:41) at renderRootSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17450:11) at performWorkOnRoot (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:16583:35) { [stack]: [Getter/Setter], [message]: 'Test error' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, TestErrorBoundary. ✓ @tanstack/react-router tests/disableGlobalCatchBoundary.test.tsx (2 tests) 178ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on first load in the route 'loader' function Error: error thrown at asyncToThrowFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at runNextTicks (node:internal/process/task_queues:65:5) at processTimers (node:internal/timers:540:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on navigate in the route 'beforeLoad' function Error: error thrown at Object.throwFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about ✓ @tanstack/react-router tests/useLocation.test.tsx (1 test) 210ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on navigate in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about ✓ @tanstack/react-router tests/useCanGoBack.test.tsx (2 tests) 109ms ✓ @tanstack/react-router tests/fileRoute.test.ts (21 tests) 6ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Error: error thrown at Object.throwFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on first load in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on navigate in the route 'beforeLoad' function Error: error thrown at Object.asyncToThrowFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on navigate in the route 'loader' function Error: error thrown at asyncToThrowFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on first load in the route 'beforeLoad' function Error: error thrown at Object.asyncToThrowFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:989:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on first load in the route 'loader' function Error: error thrown at asyncToThrowFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:25:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:691:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1030:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:11 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on navigate in the route 'beforeLoad' function Error: error thrown at Object.throwFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on navigate in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Error: error thrown at Object.throwFn [as beforeLoad] (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:515:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:549:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:554:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:546:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:557:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:988:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on first load in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: // stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > stale route errors do not leak after navigation > navigating away from a 'loader' error does not call the next route errorComponent An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > stale route errors do not leak after navigation > navigating away from a 'loader' error does not call the next route errorComponent Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:667:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:850:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:933:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1026:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2474:17 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:29:7 at Proxy.process.env.NODE_ENV.exports.startTransition (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:1158:27) at Router.Transitioner.router.startTransition (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:28:11) at /home/workflows/workspace/packages/router-core/src/router.ts:2450:12 { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > stale route errors do not leak after navigation > navigating away from a 'render' error does not call the next route errorComponent Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:29:9) at RenderErrorComponent (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:193:15) at Object.react_stack_bottom_frame (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:25904:20) at renderWithHooks (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:7662:22) at updateFunctionComponent (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:10166:19) at beginWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:11778:18) at runWithFiberInDEV (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:874:13) at performUnitOfWork (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17641:22) at workLoopSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17469:41) at renderRootSync (/home/workflows/workspace/node_modules/.pnpm/react-dom@19.2.3_react@19.2.3/node_modules/react-dom/cjs/react-dom-client.development.js:17450:11) { [stack]: [Getter/Setter], [message]: 'error thrown' } The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about stderr | tests/errorComponent.test.tsx > errorComponent receives primitive errors thrown from beforeLoad 'primitive error thrown' The above error occurred in the component. React will try to recreate this component tree from scratch using the error boundary you provided, CatchBoundaryImpl. Warning: Error in route match: /about/about ✓ @tanstack/react-router tests/errorComponent.test.tsx (39 tests) 41000ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1655ms ✓ an Error is thrown on navigate in the route 'loader' function 1550ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1510ms ✓ an Error is thrown on first load in the route 'loader' function 1512ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1073ms ✓ an Error is thrown on navigate in the route 'loader' function 1020ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1109ms ✓ an Error is thrown on first load in the route 'loader' function 1014ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1570ms ✓ an Error is thrown on navigate in the route 'loader' function 1517ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1510ms ✓ an Error is thrown on first load in the route 'loader' function 1507ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1013ms ✓ an Error is thrown on navigate in the route 'loader' function 1017ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1021ms ✓ an Error is thrown on first load in the route 'loader' function 1010ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1512ms ✓ an Error is thrown on navigate in the route 'loader' function 1514ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1535ms ✓ an Error is thrown on first load in the route 'loader' function 1510ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1014ms ✓ an Error is thrown on navigate in the route 'loader' function 1013ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1008ms ✓ an Error is thrown on first load in the route 'loader' function 1008ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1514ms ✓ an Error is thrown on navigate in the route 'loader' function 1512ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1507ms ✓ an Error is thrown on first load in the route 'loader' function 1507ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1013ms ✓ an Error is thrown on navigate in the route 'loader' function 1012ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1007ms ✓ an Error is thrown on first load in the route 'loader' function 1006ms ✓ @tanstack/react-router TS tests/link.test-d.tsx (32 tests) ✓ @tanstack/react-router TS tests/route.test-d.tsx (50 tests) ✓ @tanstack/react-router TS tests/useSearch.test-d.tsx (11 tests) ✓ @tanstack/react-router TS tests/useLoaderData.test-d.tsx (5 tests) ✓ @tanstack/react-router TS tests/useParams.test-d.tsx (5 tests) ✓ @tanstack/react-router TS tests/useRouteContext.test-d.tsx (4 tests) ✓ @tanstack/react-router TS tests/Matches.test-d.tsx (6 tests) ✓ @tanstack/react-router TS tests/router.test-d.tsx (8 tests) ✓ @tanstack/react-router TS tests/optional-path-params.test-d.tsx (12 tests) ✓ @tanstack/react-router TS tests/fileRoute.test-d.tsx (7 tests) ✓ @tanstack/react-router TS tests/routeApi.test-d.tsx (11 tests) ✓ @tanstack/react-router TS tests/useBlocker.test-d.tsx (3 tests) ✓ @tanstack/react-router TS tests/useRouterState.test-d.tsx (1 test) ✓ @tanstack/react-router TS tests/useMatch.test-d.tsx (4 tests) ✓ @tanstack/react-router TS tests/useNavigate.test-d.tsx (3 tests) ✓ @tanstack/react-router TS tests/useLocation.test-d.tsx (2 tests) ✓ @tanstack/react-router TS tests/RouterProvider.test-d.tsx (1 test) ✓ @tanstack/react-router TS tests/redirects.test-d.tsx (1 test) ⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯ Vitest caught 1 unhandled error during the test run. This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected. ⎯⎯⎯ Unhandled Source Error ⎯⎯⎯ TypeCheckError: Object literal may only specify known properties, and 'foo' does not exist in type 'Partial> | "root"[]'. ❯ tests/link.test.tsx:5895:31 5893| middlewares: [ 5894| // this means we cannot get the correct input type for this … 5895| stripSearchParams({ foo: 'default' }), | ^ 5896| retainSearchParams(true), 5897| ], ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Test Files 44 passed (44) Tests 911 passed | 1 skipped (912) Type Errors no errors Errors 1 error Start at 18:43:22 Duration 85.52s (transform 3.35s, setup 3.17s, import 11.71s, tests 89.32s, environment 14.34s, typecheck 17.01s) [ELIFECYCLE] Command failed with exit code 1. TASK ID: @tanstack/solid-router:test:unit $ vitest && vitest --mode server The plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the resolve.tsconfigPaths option. You can remove the plugin and set resolve.tsconfigPaths: true in your Vite config instead. Testing types with tsc and vue-tsc is an experimental feature. Breaking changes might not follow SemVer, please pin Vitest's version when using it. RUN v4.1.4 /home/workflows/workspace/packages/solid-router stdout | tests/routeContext.test.tsx > context function > context is executed > when the path params change [ [ [Object: null prototype] { id: 1 } ] ] stderr | tests/link.test.tsx > Link > when the current route is the root with beforeLoad that throws Warning: Error in route match: __root__ stderr | tests/link.test.tsx > Link > when navigating to /posts with invalid search Warning: Error in route match: /posts stderr | tests/link.test.tsx > Link > when navigating to /posts with a loader that errors Warning: Error in route match: /posts stderr | tests/link.test.tsx > Link > when navigating away from a route with a loader that errors Warning: Error in route match: /posts stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that throws an error Warning: Error in route match: /posts stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that throws an error bubbles to the root Warning: Error in route match: __root__ stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that throws an error bubbles to the nearest parent Warning: Error in route match: /posts stderr | tests/link.test.tsx > Link > when navigating to the root with an error in component Warning: Error in route match: __root__ Error: Not implemented: navigation (except hash changes) at module.exports (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/browser/not-implemented.js:9:17) at navigateFetch (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/window/navigation.js:77:3) at exports.navigate (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/window/navigation.js:55:3) at Timeout._onTimeout (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/nodes/HTMLHyperlinkElementUtils-impl.js:81:7) at listOnTimeout (node:internal/timers:608:17) at processTimers (node:internal/timers:543:7) undefined Error: Not implemented: navigation (except hash changes) at module.exports (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/browser/not-implemented.js:9:17) at navigateFetch (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/window/navigation.js:77:3) at exports.navigate (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/window/navigation.js:55:3) at Timeout._onTimeout (/home/workflows/workspace/node_modules/.pnpm/jsdom@25.0.1/node_modules/jsdom/lib/jsdom/living/nodes/HTMLHyperlinkElementUtils-impl.js:81:7) at listOnTimeout (node:internal/timers:608:17) at processTimers (node:internal/timers:543:7) undefined stderr | tests/link.test.tsx > relative links with { basepath: '' } > should navigate to a child link based on pathname Warning: A notFoundError was encountered on the route with ID "/param/$param/a", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) ✓ @tanstack/solid-router tests/link.test.tsx (127 tests) 8578ms ✓ when a Link is disabled 1120ms ✓ updates exact and fuzzy active state before the next route renders 518ms ✓ updates exact active state and href when only params change with params=true 512ms ✓ updates search-sensitive active state immediately with and without search=true 516ms ✓ when navigating away from a route with a loader that errors 1612ms ✓ when preloading /post/$postId with a beforeLoad that navigates to /login 364ms ✓ Router.preload="intent", pendingComponent renders during unresolved route loader 709ms ✓ should respect target attribute set by custom component 1010ms stderr | tests/useNavigate.test.tsx > when navigating from /invoices to ./invoiceId and the current route is /posts/$postId/details Could not find match for from: /invoices ✓ @tanstack/solid-router tests/useNavigate.test.tsx (44 tests) 1409ms ✓ @tanstack/solid-router tests/routeContext.test.tsx (69 tests | 1 skipped) 13768ms ✓ modified route context, present in the index route 306ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in the beforeLoad of the index route 309ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in the loader of the index route 311ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the beforeLoad of the /about route 317ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the loader of the /about route 312ms ✓ nested destination on navigate, route context in the /nested/about route is correctly inherited from the /nested parent 310ms ✓ nested destination on navigate, when a redirect is thrown in beforeLoad in /about, the /nested/person route context is correctly inherited from its parent /nested 462ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from parent /nested 460ms ✓ _layout on first-load, route context in the index route is correctly inherited from the layout parent 306ms ✓ _layout on navigate, route context in the /about route is correctly inherited from the layout parent 312ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 462ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 463ms ✓ modified route context, present in the index route 304ms ✓ on navigate (with preload), loader isn't invoked with undefined context if beforeLoad is pending when navigation happens 313ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in beforeLoad of the index route 306ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in loader of the index route 319ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the beforeLoad of the /about route 312ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the loader of the /about route 313ms ✓ nested destination on navigate, route context in the /nested/about route is correctly inherited from the /nested parent 316ms ✓ nested destination on navigate, when a redirect is thrown in beforeLoad in /about, the /nested/person route context is correctly inherited from its parent /nested 466ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from parent /nested 461ms ✓ _layout on first-load, route context in the index route is correctly inherited from the layout parent 331ms ✓ _layout on navigate, route context in the /about route is correctly inherited from the layout parent 310ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 491ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 461ms ✓ route context, (sleep in beforeLoad), with immediate navigation 334ms ✓ nested destination on navigate, when a redirect is thrown in beforeLoad in /about, the /nested/person route context is correctly inherited from its parent /nested 313ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from its parent /nested 337ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 312ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 312ms stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > does not throw an error when the search param is valid Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > throws an error when the search param is not valid Warning: Error in route match: __root__ Warning: Error in route match: __root__ stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > does not throw an error when the search param is valid Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > throws an error when the search param is not valid Warning: Error in route match: __root__ stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > does not throw an error when the search param is valid Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > search params in URL > validates search params > search param validation > throws an error when the search param is not valid Warning: Error in route match: __root__ Warning: Error in route match: __root__ ✓ @tanstack/solid-router tests/navigate.test.tsx (54 tests) 275ms stderr | tests/router.test.tsx > does not strip search params if search validation fails > root is missing Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: [ { "expected": "string", "code": "invalid_type", "path": [ "root" ], "message": "Invalid input: expected string, received undefined" } ] stderr | tests/router.test.tsx > does not strip search params if search validation fails > index is missing Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: [ { "expected": "string", "code": "invalid_type", "path": [ "index" ], "message": "Invalid input: expected string, received undefined" } ] stderr | tests/router.test.tsx > statusCode reset on navigation > should reset statusCode to 200 when navigating from 404 to valid route Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > statusCode reset on navigation > should reset statusCode to 200 when navigating from 404 to valid route Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) stderr | tests/router.test.tsx > statusCode reset on navigation > status code is set when loader/beforeLoad throws (isAsync=true) > should set statusCode to 500 when a route loader throws an Error Warning: Error in route match: /loader-throws-error Warning: Error in route match: /loader-throws-error stderr | tests/router.test.tsx > statusCode reset on navigation > status code is set when loader/beforeLoad throws (isAsync=true) > should set statusCode to 500 when a route beforeLoad throws an Error Warning: Error in route match: /beforeload-throws-error stderr | tests/router.test.tsx > statusCode reset on navigation > status code is set when loader/beforeLoad throws (isAsync=true) > should set statusCode to 500 when a route beforeLoad throws an Error Warning: Error in route match: /beforeload-throws-error stderr | tests/router.test.tsx > statusCode reset on navigation > status code is set when loader/beforeLoad throws (isAsync=false) > should set statusCode to 500 when a route loader throws an Error Warning: Error in route match: /loader-throws-error Warning: Error in route match: /loader-throws-error stderr | tests/router.test.tsx > statusCode reset on navigation > status code is set when loader/beforeLoad throws (isAsync=false) > should set statusCode to 500 when a route beforeLoad throws an Error Warning: Error in route match: /beforeload-throws-error Warning: Error in route match: /beforeload-throws-error ✓ @tanstack/solid-router tests/router.test.tsx (129 tests) 3006ms ✓ re-runs loaders that throw notFound() when invalidated via HMR filter 513ms ✓ keeps rendering a route notFoundComponent when loader returns notFound() after invalidate 507ms ✓ @tanstack/solid-router tests/optional-path-params.test.tsx (29 tests) 590ms stdout | tests/loaders.test.tsx > reproducer for #2031 beforeload called beforeload called stdout | tests/loaders.test.tsx > reproducer for #2031 beforeload called stdout | tests/loaders.test.tsx > reproducer for #2053 beforeload called stdout | tests/loaders.test.tsx > reproducer for #2053 beforeload called stderr | tests/loaders.test.tsx > reproducer for #2198 - throw error from beforeLoad upon initial load Warning: Error in route match: / stderr | tests/loaders.test.tsx > throw error from loader upon initial load Warning: Error in route match: / stderr | tests/loaders.test.tsx > throw error from beforeLoad when navigating to route Warning: Error in route match: /foo stderr | tests/loaders.test.tsx > cancelMatches after pending timeout Warning: A notFoundError was encountered on the route with ID "__root__", but a notFoundComponent option was not configured, nor was a router level defaultNotFoundComponent configured. Consider configuring at least one of these to avoid TanStack Router's overly generic defaultNotFoundComponent (

Not Found

) ✓ @tanstack/solid-router tests/route.test.tsx (26 tests) 1027ms ✓ @tanstack/solid-router tests/useBlocker.test.tsx (10 tests) 332ms ✓ @tanstack/solid-router tests/loaders.test.tsx (14 tests) 5011ms ✓ reproducer #4245 518ms ✓ clears pendingTimeout when match resolves 509ms ✓ cancelMatches after pending timeout 3013ms ✓ @tanstack/solid-router tests/Scripts.test.tsx (9 tests) 443ms ✓ @tanstack/solid-router tests/not-found.test.tsx (9 tests) 183ms ✓ @tanstack/solid-router tests/index.test.tsx (1 test) 4ms ✓ @tanstack/solid-router tests/Matches.test.tsx (25 tests) 1103ms ✓ should show pendingComponent of root route 512ms ✓ @tanstack/solid-router tests/redirect.test.tsx (6 tests) 1378ms ✓ when `redirect` is thrown in `beforeLoad` 400ms ✓ when root `beforeLoad` redirects while root pendingComponent is showing and the target route is lazy 512ms ✓ @tanstack/solid-router tests/store-updates-during-navigation.test.tsx (10 tests) 1892ms ✓ async loader, async beforeLoad, pendingMs 632ms ✓ sync beforeLoad 416ms ✓ @tanstack/solid-router tests/useParams.test.tsx (1 test) 216ms ✓ @tanstack/solid-router tests/searchMiddleware.test.tsx (5 tests) 203ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on navigate in the route 'beforeLoad' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on navigate in the route 'loader' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on first load in the route 'loader' function Warning: Error in route match: / ✓ @tanstack/solid-router tests/blocker.test.tsx (13 tests) 4439ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'postsLink' 1015ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'postsLink' 1015ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'button' 1013ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'button' 1009ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on navigate in the route 'beforeLoad' function Warning: Error in route match: /about ✓ @tanstack/solid-router tests/renderRouterToStream.test.tsx (2 tests) 28ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on navigate in the route 'loader' function Warning: Error in route match: /about stderr | tests/useMatch.test.tsx > useMatch > when match is not found > throws if shouldThrow = undefined Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: Invariant failed: Could not find an active match from "/posts" stderr | tests/useMatch.test.tsx > useMatch > when match is not found > throws if shouldThrow = true Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: Invariant failed: Could not find an active match from "/posts" ✓ @tanstack/solid-router tests/useMatch.test.tsx (7 tests) 183ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on first load in the route 'loader' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on navigate in the route 'beforeLoad' function Warning: Error in route match: /about ✓ @tanstack/solid-router tests/createLazyRoute.test.tsx (2 tests) 2589ms ✓ should wait for lazy options to be streamed in before 2540ms ✓ @tanstack/solid-router tests/ClientOnly.test.tsx (2 tests) 53ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on navigate in the route 'loader' function Warning: Error in route match: /about ✓ @tanstack/solid-router tests/useCanGoBack.test.tsx (2 tests) 70ms stderr | tests/disableGlobalCatchBoundary.test.tsx > disableGlobalCatchBoundary option > catches errors in global boundary when disableGlobalCatchBoundary is false Warning: The following error wasn't caught by any route! At the very least, consider setting an 'errorComponent' in your RootRoute! Warning: Test error ✓ @tanstack/solid-router tests/disableGlobalCatchBoundary.test.tsx (2 tests) 147ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / ✓ @tanstack/solid-router tests/fileRoute.test.ts (21 tests) 8ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on first load in the route 'loader' function Warning: Error in route match: / ✓ @tanstack/solid-router tests/Transitioner.test.tsx (1 test) 34ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on navigate in the route 'beforeLoad' function Warning: Error in route match: /about ✓ @tanstack/solid-router tests/RouterProvider.test.tsx (1 test) 38ms stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on navigate in the route 'loader' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=true > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on first load in the route 'loader' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on navigate in the route 'beforeLoad' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on navigate in the route 'loader' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=true > an Error is thrown on first load in the route 'loader' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on navigate in the route 'beforeLoad' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on navigate in the route 'loader' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload=false > with async=false > an Error is thrown on first load in the route 'loader' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on navigate in the route 'beforeLoad' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on navigate in the route 'loader' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=true > an Error is thrown on first load in the route 'loader' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on navigate in the route 'beforeLoad' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on navigate in the route 'loader' function Warning: Error in route match: /about stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / stderr | tests/errorComponent.test.tsx > with lazy errorComponent=false > errorComponent is rendered when the preload='intent' > with async=false > an Error is thrown on first load in the route 'loader' function Warning: Error in route match: / ✓ @tanstack/solid-router tests/errorComponent.test.tsx (32 tests) 40476ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1698ms ✓ an Error is thrown on navigate in the route 'loader' function 1518ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1509ms ✓ an Error is thrown on first load in the route 'loader' function 1506ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1011ms ✓ an Error is thrown on navigate in the route 'loader' function 1012ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1006ms ✓ an Error is thrown on first load in the route 'loader' function 1007ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1515ms ✓ an Error is thrown on navigate in the route 'loader' function 1516ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1506ms ✓ an Error is thrown on first load in the route 'loader' function 1507ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1020ms ✓ an Error is thrown on navigate in the route 'loader' function 1010ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1005ms ✓ an Error is thrown on first load in the route 'loader' function 1005ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1511ms ✓ an Error is thrown on navigate in the route 'loader' function 1510ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1505ms ✓ an Error is thrown on first load in the route 'loader' function 1505ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1014ms ✓ an Error is thrown on navigate in the route 'loader' function 1009ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1005ms ✓ an Error is thrown on first load in the route 'loader' function 1005ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1510ms ✓ an Error is thrown on navigate in the route 'loader' function 1510ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1505ms ✓ an Error is thrown on first load in the route 'loader' function 1506ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1011ms ✓ an Error is thrown on navigate in the route 'loader' function 1009ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1005ms ✓ an Error is thrown on first load in the route 'loader' function 1004ms ✓ @tanstack/solid-router TS tests/link.test-d.tsx (30 tests) ✓ @tanstack/solid-router TS tests/route.test-d.tsx (50 tests) ✓ @tanstack/solid-router TS tests/useSearch.test-d.tsx (11 tests) ✓ @tanstack/solid-router TS tests/useLoaderData.test-d.tsx (5 tests) ✓ @tanstack/solid-router TS tests/useRouteContext.test-d.tsx (4 tests) ✓ @tanstack/solid-router TS tests/useParams.test-d.tsx (5 tests) ✓ @tanstack/solid-router TS tests/Matches.test-d.tsx (6 tests) ✓ @tanstack/solid-router TS tests/router.test-d.tsx (8 tests) ✓ @tanstack/solid-router TS tests/optional-path-params.test-d.tsx (12 tests) ✓ @tanstack/solid-router TS tests/fileRoute.test-d.tsx (6 tests) ✓ @tanstack/solid-router TS tests/routeApi.test-d.tsx (9 tests) ✓ @tanstack/solid-router TS tests/useBlocker.test-d.tsx (3 tests) ✓ @tanstack/solid-router TS tests/useMatch.test-d.tsx (4 tests) ✓ @tanstack/solid-router TS tests/useNavigate.test-d.tsx (3 tests) ✓ @tanstack/solid-router TS tests/useRouterState.test-d.tsx (1 test) ✓ @tanstack/solid-router TS tests/useLocation.test-d.tsx (2 tests) ✓ @tanstack/solid-router TS tests/RouterProvider.test-d.tsx (1 test) ✓ @tanstack/solid-router TS tests/redirects.test-d.tsx (1 test) ⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯ Vitest caught 1 unhandled error during the test run. This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected. ⎯⎯⎯ Unhandled Source Error ⎯⎯⎯ TypeCheckError: Object literal may only specify known properties, and 'foo' does not exist in type 'Partial> | "root"[]'. ❯ tests/link.test.tsx:5766:31 5764| middlewares: [ 5765| // this means we cannot get the correct input type for this … 5766| stripSearchParams({ foo: 'default' }), | ^ 5767| retainSearchParams(true), 5768| ], ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Test Files 46 passed (46) Tests 813 passed | 1 skipped (814) Type Errors no errors Errors 1 error Start at 18:43:22 Duration 95.28s (transform 9.66s, setup 4.59s, import 16.89s, tests 87.48s, environment 16.54s, typecheck 16.66s) [ELIFECYCLE] Command failed with exit code 1. TASK ID: @tanstack/vue-router:test:unit $ vitest 6:43:22 PM [vite] warning: `esbuild` option was specified by "vite:vue-jsx" plugin. This option is deprecated, please use `oxc` instead. The plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the resolve.tsconfigPaths option. You can remove the plugin and set resolve.tsconfigPaths: true in your Vite config instead. Both esbuild and oxc options were set. oxc options will be used and esbuild options will be ignored. The following esbuild options were set: `{ include: /\.ts$/ }` Testing types with tsc and vue-tsc is an experimental feature. Breaking changes might not follow SemVer, please pin Vitest's version when using it. RUN v4.1.4 /home/workflows/workspace/packages/vue-router stdout | tests/routeContext.test.tsx > context function > context is executed > when the path params change is an experimental feature and its API will likely change. stdout | tests/link.test.tsx > Link > when a Link is disabled is an experimental feature and its API will likely change. stdout | tests/routeContext.test.tsx > context function > context is executed > when the path params change [ [ [Object: null prototype] { id: 1 } ] ] stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that throws an error bubbles to the root Warning: Error in route match: __root__/ stderr | tests/link.test.tsx > Link > when navigating to /posts with a beforeLoad that throws an error bubbles to the nearest parent Warning: Error in route match: /posts/posts stderr | tests/link.test.tsx > Link > when navigating to the root with an error in component Warning: Error in route match: __root__/ Warning: Error in route match: __root__/ stderr | tests/link.test.tsx > createLink > should pass activeProps and inactiveProps to the custom link [Vue warn]: Non-function value encountered for default slot. Prefer function slots for better performance. at