TASK ID: @tanstack/react-router:test:unit $ vitest 11:57:18 AM [vite] warning: `esbuild` option was specified by "vite:react-babel" plugin. This option is deprecated, please use `oxc` instead. 11:57:18 AM [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: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "search" ], "message": "Required" } ] at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3030:13) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1459:13) ... 6 lines matching cause stack trace ... at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) at /home/workflows/workspace/packages/react-router/tests/router.test.tsx:1888:32 { [stack]: [Getter/Setter], [message]: '[\n' + ' {\n' + ' "code": "invalid_type",\n' + ' "expected": "string",\n' + ' "received": "undefined",\n' + ' "path": [\n' + ' "search"\n' + ' ],\n' + ' "message": "Required"\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:3024:48) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1459:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1385:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2388:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2418:14 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [stack]: [Getter/Setter], [message]: 'validation failed', name: 'TestValidationError', issues: [ { code: 'invalid_type', expected: 'string', received: 'undefined', path: [ 'search', [length]: 1 ], message: 'Required' }, [length]: 1 ] }, routerCode: 'VALIDATE_SEARCH' } 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:1471:32) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1385:17) ... 5 lines matching cause stack trace ... at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) at /home/workflows/workspace/packages/react-router/tests/router.test.tsx:1888:32 at process.env.NODE_ENV.exports.act (/home/workflows/workspace/node_modules/.pnpm/react@19.2.3/node_modules/react/cjs/react.development.js:814:22) { [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:3038:27) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1459:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1385:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2388:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2418:14 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [stack]: [Getter/Setter], [message]: 'validation failed', name: 'TestValidationError', issues: [ { message: 'search must be a string' }, [length]: 1 ] }, routerCode: 'VALIDATE_SEARCH' } 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: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "root" ], "message": "Required" } ] at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3030:13) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1459:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1385:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2388:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2418:14 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) at tryLoad (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:81:22) { [stack]: [Getter/Setter], [message]: '[\n' + ' {\n' + ' "code": "invalid_type",\n' + ' "expected": "string",\n' + ' "received": "undefined",\n' + ' "path": [\n' + ' "root"\n' + ' ],\n' + ' "message": "Required"\n' + ' }\n' + ']', [cause]: { issues: [ { code: 'invalid_type', expected: 'string', received: 'undefined', path: [ 'root', [length]: 1 ], message: 'Required' }, [length]: 1 ] }, routerCode: 'VALIDATE_SEARCH' } 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: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "root" ], "message": "Required" } ] stderr | tests/router.test.tsx > does not strip search params if search validation fails > index is missing SearchParamError: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "index" ], "message": "Required" } ] at validateSearch (/home/workflows/workspace/packages/router-core/src/router.ts:3030:13) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1459:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1385:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2388:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2418:14 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) at tryLoad (/home/workflows/workspace/packages/react-router/src/Transitioner.tsx:81:22) { [stack]: [Getter/Setter], [message]: '[\n' + ' {\n' + ' "code": "invalid_type",\n' + ' "expected": "string",\n' + ' "received": "undefined",\n' + ' "path": [\n' + ' "index"\n' + ' ],\n' + ' "message": "Required"\n' + ' }\n' + ']', [cause]: { issues: [ { code: 'invalid_type', expected: 'string', received: 'undefined', path: [ 'index', [length]: 1 ], message: 'Required' }, [length]: 1 ] }, routerCode: 'VALIDATE_SEARCH' } 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: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "index" ], "message": "Required" } ] 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:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'test-error', routerCode: 'BEFORE_LOAD' } 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:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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 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) 2875ms 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:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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!', routerCode: 'BEFORE_LOAD' } 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:1471:32) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1385:17) ... 5 lines matching cause stack trace ... at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) at /home/workflows/workspace/packages/history/src/index.ts:121:41 at Set.forEach () { [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:3042:12) at Router.matchRoutesInternal (/home/workflows/workspace/packages/router-core/src/router.ts:1459:13) at RouterCore.matchRoutes (/home/workflows/workspace/packages/router-core/src/router.ts:1385:17) at RouterCore.beforeLoad (/home/workflows/workspace/packages/router-core/src/router.ts:2388:33) at /home/workflows/workspace/packages/router-core/src/router.ts:2418:14 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [stack]: [Getter/Setter], [message]: 'Not a number!' }, routerCode: 'VALIDATE_SEARCH' } 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:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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!', routerCode: 'BEFORE_LOAD' } 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:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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!', routerCode: 'BEFORE_LOAD' } 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:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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!', routerCode: 'BEFORE_LOAD' } 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) 9109ms ✓ when a Link is disabled 1099ms ✓ updates exact and fuzzy active state before the next route renders 581ms ✓ updates exact active state and href when only params change with params=true 543ms ✓ updates search-sensitive active state immediately with and without search=true 563ms ✓ when navigating away from a route with a loader that errors 1029ms ✓ Router.preload="intent", pendingComponent renders during unresolved route loader 719ms ✓ 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 An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act An update to Transitioner inside a test was not wrapped in act(...). When testing, code that causes React state updates should be wrapped into act(...): act(() => { /* fire events that update state */ }); /* assert on the output */ This ensures that you're 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) 1068ms ✓ @tanstack/react-router tests/navigate.test.tsx (56 tests) 246ms ✓ @tanstack/react-router tests/optional-path-params.test.tsx (29 tests) 742ms hello empty type ✓ @tanstack/react-router tests/Scripts.test.tsx (16 tests) 850ms ✓ @tanstack/react-router tests/routeContext.test.tsx (77 tests | 1 skipped) 14849ms ✓ modified route context, present in the index route 309ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in the beforeLoad of the index route 314ms ✓ on first-load, route context is present in the /about route after a redirect is thrown in the 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 321ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the loader of the /about route 322ms ✓ 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 465ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from parent /nested 474ms ✓ _layout on first-load, route context in the index route is correctly inherited from the layout parent 312ms ✓ _layout on navigate, route context in the /about route is correctly inherited from the layout parent 319ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 467ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 473ms ✓ 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 322ms ✓ 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 335ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the loader of the /about route 331ms ✓ nested destination on navigate, route context in the /nested/about route is correctly inherited from the /nested parent 326ms ✓ 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 519ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from parent /nested 570ms ✓ _layout on first-load, route context in the index route is correctly inherited from the layout parent 329ms ✓ _layout on navigate, route context in the /about route is correctly inherited from the layout parent 347ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 473ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 494ms ✓ route context, (sleep in beforeLoad), with immediate navigation 480ms ✓ 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 339ms ✓ 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 363ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 410ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 344ms 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:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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!', routerCode: 'BEFORE_LOAD' } 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:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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!', routerCode: 'BEFORE_LOAD' } 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 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/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 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:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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! ✓ @tanstack/react-router tests/route.test.tsx (26 tests) 1406ms 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 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) 495ms ✓ does not block navigation when not enabled 306ms ✓ @tanstack/react-router tests/loaders.test.tsx (14 tests) 6244ms ✓ parentMatchPromise is defined in a child route 306ms ✓ reproducer #4245 612ms ✓ clears pendingTimeout when match resolves 582ms ✓ cancelMatches after pending timeout 3093ms ✓ reproducer for #6388 - rapid navigation between parameterized routes should not trigger errorComponent 593ms 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 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 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 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 { 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 { 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 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 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/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 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 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 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 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/not-found.test.tsx (8 tests) 605ms ✓ @tanstack/react-router tests/redirect.test.tsx (6 tests) 1479ms ✓ when `redirect` is thrown in `beforeLoad` 396ms ✓ when root `beforeLoad` redirects while root pendingComponent is showing and the target route is lazy 552ms 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:24:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'error thrown', routerCode: 'BEFORE_LOAD' } 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=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:24:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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/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

) ✓ @tanstack/react-router tests/Matches.test.tsx (24 tests) 1627ms ✓ when filtering useMatches by loaderData 331ms ✓ should show pendingComponent of root route 582ms 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:24:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'error thrown', routerCode: 'BEFORE_LOAD' } 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:24:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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/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) 309ms 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:28:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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=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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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=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:28:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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/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/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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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 > 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 | 2 failed) 1973ms × async loader, async beforeLoad, pendingMs 692ms ✓ redirection in preload 17ms × sync beforeLoad 481ms ✓ nothing 34ms ✓ not found in beforeLoad 47ms ✓ hover preload, then navigate, w/ async loaders 176ms ✓ navigate, w/ preloaded & async loaders 166ms ✓ navigate, w/ preloaded & sync loaders 30ms ✓ navigate, w/ previous navigation & async loader 181ms ✓ preload a preloaded route w/ async loader 146ms 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:24:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'error thrown', routerCode: 'BEFORE_LOAD' } 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/searchMiddleware.test.tsx (5 tests) 417ms 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:24:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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=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:24:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'error thrown', routerCode: 'BEFORE_LOAD' } 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:24:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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:28:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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/blocker.test.tsx (13 tests) 4545ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'postsLink' 1020ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'postsLink' 1019ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'button' 1013ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'button' 1016ms 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:28:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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 first load in the route 'loader' function Error: error thrown at throwFn (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:28:9) at RenderErrorComponent (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:188: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:24:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'error thrown', routerCode: 'BEFORE_LOAD' } 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:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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) 2657ms ✓ should wait for lazy options to be streamed in before 2539ms 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:24:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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) 245ms ✓ @tanstack/react-router tests/ClientOnly.test.tsx (3 tests) 132ms 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:24:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'error thrown', routerCode: 'BEFORE_LOAD' } 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/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) 176ms 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:24:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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:28:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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) 187ms 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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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) 149ms 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:28:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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/fileRoute.test.ts (21 tests) 56ms 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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:24:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'error thrown', routerCode: 'BEFORE_LOAD' } 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:24:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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:24:9) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1010:34) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [stack]: [Getter/Setter], [message]: 'error thrown', routerCode: 'BEFORE_LOAD' } 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:24:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:711:13) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:7) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:7) at async Promise.all (index 1) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1055:5) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:9 { [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:28:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:28:9) at executeBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:535:39) at execute (/home/workflows/workspace/packages/router-core/src/load-matches.ts:569:25) at queueExecution (/home/workflows/workspace/packages/router-core/src/load-matches.ts:574:55) at serverSsr (/home/workflows/workspace/packages/router-core/src/load-matches.ts:566:12) at handleBeforeLoad (/home/workflows/workspace/packages/router-core/src/load-matches.ts:577:10) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1009:26) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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', routerCode: 'BEFORE_LOAD' } 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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:28:9) at runLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:687:28) at handleLoader (/home/workflows/workspace/packages/router-core/src/load-matches.ts:870:13) at loadRouteMatch (/home/workflows/workspace/packages/router-core/src/load-matches.ts:953:13) at loadMatches (/home/workflows/workspace/packages/router-core/src/load-matches.ts:1051:24) at /home/workflows/workspace/packages/router-core/src/router.ts:2435:15 at /home/workflows/workspace/packages/react-router/src/Transitioner.tsx:33: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:32:11) at RouterCore.load (/home/workflows/workspace/packages/router-core/src/router.ts:2416:10) { [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:28:9) at RenderErrorComponent (/home/workflows/workspace/packages/react-router/tests/errorComponent.test.tsx:188: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 ✓ @tanstack/react-router tests/errorComponent.test.tsx (37 tests) 41513ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1908ms ✓ an Error is thrown on navigate in the route 'loader' function 1598ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1531ms ✓ an Error is thrown on first load in the route 'loader' function 1570ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1098ms ✓ an Error is thrown on navigate in the route 'loader' function 1040ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1017ms ✓ an Error is thrown on first load in the route 'loader' function 1018ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1566ms ✓ an Error is thrown on navigate in the route 'loader' function 1577ms ✓ 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 1021ms ✓ an Error is thrown on navigate in the route 'loader' function 1034ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1010ms ✓ an Error is thrown on first load in the route 'loader' function 1011ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1524ms ✓ an Error is thrown on navigate in the route 'loader' function 1523ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1526ms ✓ an Error is thrown on first load in the route 'loader' function 1512ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1047ms ✓ an Error is thrown on navigate in the route 'loader' function 1025ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1009ms ✓ an Error is thrown on first load in the route 'loader' function 1006ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1513ms ✓ an Error is thrown on navigate in the route 'loader' function 1514ms ✓ 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 1508ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1017ms ✓ 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 ✓ @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) ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯ FAIL @tanstack/react-router tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > async loader, async beforeLoad, pendingMs AssertionError: expected 8 to be 7 // Object.is equality - Expected + Received - 7 + 8 ❯ tests/store-updates-during-navigation.test.tsx:139:21 137| // that needs to be done during a navigation. 138| // Any change that increases this number should be investigated. 139| expect(updates).toBe(7) | ^ 140| }) 141| ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯ FAIL @tanstack/react-router tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > sync beforeLoad AssertionError: expected 5 to be 4 // Object.is equality - Expected + Received - 4 + 5 ❯ tests/store-updates-during-navigation.test.tsx:173:21 171| // that needs to be done during a navigation. 172| // Any change that increases this number should be investigated. 173| expect(updates).toBe(4) | ^ 174| }) 175| ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/2]⎯ Test Files 1 failed | 42 passed (43) Tests 2 failed | 898 passed | 1 skipped (901) Type Errors no errors Start at 11:57:18 Duration 94.48s (transform 3.19s, setup 4.29s, import 13.24s, tests 93.95s, environment 18.19s, typecheck 20.38s) [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) 9082ms ✓ when a Link is disabled 1167ms ✓ updates exact and fuzzy active state before the next route renders 528ms ✓ updates exact active state and href when only params change with params=true 515ms ✓ updates search-sensitive active state immediately with and without search=true 535ms ✓ when navigating away from a route with a loader that errors 1619ms ✓ when preloading /post/$postId with a beforeLoad that navigates to /login 366ms ✓ Router.preload="intent", pendingComponent renders during unresolved route loader 709ms ✓ should respect target attribute set by custom component 1008ms 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) 1767ms ✓ @tanstack/solid-router tests/routeContext.test.tsx (69 tests | 1 skipped) 14048ms ✓ modified route context, present in the index route 307ms ✓ 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 310ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the beforeLoad of the /about route 322ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the loader of the /about route 317ms ✓ nested destination on navigate, route context in the /nested/about route is correctly inherited from the /nested parent 317ms ✓ 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 464ms ✓ _layout on first-load, route context in the index route is correctly inherited from the layout parent 309ms ✓ _layout on navigate, route context in the /about route is correctly inherited from the layout parent 318ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 469ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 469ms ✓ 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 329ms ✓ 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 306ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the beforeLoad of the /about route 309ms ✓ on navigate, route context is present in the /person route after a redirect is thrown in the loader of the /about route 310ms ✓ nested destination on navigate, route context in the /nested/about route is correctly inherited from the /nested parent 311ms ✓ 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 464ms ✓ nested destination on navigate, when a redirect is thrown in loader in /about, the /nested/person route context is correctly inherited from parent /nested 483ms ✓ _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 313ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 475ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 476ms ✓ route context, (sleep in beforeLoad), with immediate navigation 333ms ✓ 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 318ms ✓ 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 335ms ✓ _layout on navigate, when a redirect is thrown in beforeLoad in /about, the /person route context is correctly inherited from the layout parent 327ms ✓ _layout on navigate, when a redirect is thrown in loader in /about, the /person route context is correctly inherited from the layout parent 355ms ✓ @tanstack/solid-router tests/navigate.test.tsx (54 tests) 332ms 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__ 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 > 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: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "root" ], "message": "Required" } ] 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: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "index" ], "message": "Required" } ] 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 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 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 ✓ @tanstack/solid-router tests/router.test.tsx (129 tests) 4192ms ✓ re-runs loaders that throw notFound() when invalidated via HMR filter 544ms ✓ keeps rendering a route notFoundComponent when loader returns notFound() after invalidate 541ms ✓ @tanstack/solid-router tests/optional-path-params.test.tsx (29 tests) 624ms 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) 1022ms ✓ @tanstack/solid-router tests/useBlocker.test.tsx (10 tests) 518ms ✓ @tanstack/solid-router tests/loaders.test.tsx (14 tests) 5134ms ✓ reproducer #4245 572ms ✓ clears pendingTimeout when match resolves 511ms ✓ cancelMatches after pending timeout 3052ms ✓ @tanstack/solid-router tests/not-found.test.tsx (9 tests) 490ms ✓ @tanstack/solid-router tests/Scripts.test.tsx (7 tests) 774ms ✓ keeps manifest stylesheet links mounted across repeated Link navigations 441ms ✓ @tanstack/solid-router tests/index.test.tsx (1 test) 5ms ✓ @tanstack/solid-router tests/Matches.test.tsx (25 tests) 1081ms ✓ should show pendingComponent of root route 528ms ✓ @tanstack/solid-router tests/redirect.test.tsx (6 tests) 1374ms ✓ when `redirect` is thrown in `beforeLoad` 320ms ✓ when root `beforeLoad` redirects while root pendingComponent is showing and the target route is lazy 534ms ✓ @tanstack/solid-router tests/useParams.test.tsx (1 test) 177ms ❯ @tanstack/solid-router tests/store-updates-during-navigation.test.tsx (10 tests | 3 failed) 1812ms × async loader, async beforeLoad, pendingMs 613ms ✓ redirection in preload 12ms × sync beforeLoad 474ms ✓ nothing 21ms × not found in beforeLoad 52ms ✓ hover preload, then navigate, w/ async loaders 167ms ✓ navigate, w/ preloaded & async loaders 131ms ✓ navigate, w/ preloaded & sync loaders 35ms ✓ navigate, w/ previous navigation & async loader 177ms ✓ preload a preloaded route w/ async loader 128ms 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 ✓ @tanstack/solid-router tests/searchMiddleware.test.tsx (5 tests) 272ms 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: / 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 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 ✓ @tanstack/solid-router tests/blocker.test.tsx (13 tests) 4462ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'postsLink' 1018ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'postsLink' 1012ms ✓ blocks navigation with condition = undefined, ignoreBlocker = undefined, clickTarget = 'button' 1011ms ✓ 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=false > with async=false > an Error is thrown on first load in the route 'beforeLoad' function Warning: Error in route match: / 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) 224ms 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) 2625ms ✓ should wait for lazy options to be streamed in before 2547ms 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/ClientOnly.test.tsx (2 tests) 56ms 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/useCanGoBack.test.tsx (2 tests) 109ms 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: / 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) 152ms 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/fileRoute.test.ts (21 tests) 6ms 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: / ✓ @tanstack/solid-router tests/Transitioner.test.tsx (1 test) 65ms 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: / ✓ @tanstack/solid-router tests/RouterProvider.test.tsx (1 test) 42ms 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) 40800ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1787ms ✓ an Error is thrown on navigate in the route 'loader' function 1590ms ✓ 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 1510ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1022ms ✓ an Error is thrown on navigate in the route 'loader' function 1021ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1010ms ✓ an Error is thrown on first load in the route 'loader' function 1011ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1528ms ✓ an Error is thrown on navigate in the route 'loader' function 1528ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1522ms ✓ an Error is thrown on first load in the route 'loader' function 1514ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1024ms ✓ an Error is thrown on navigate in the route 'loader' function 1020ms ✓ an Error is thrown on first load in the route 'beforeLoad' function 1042ms ✓ an Error is thrown on first load in the route 'loader' function 1007ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1518ms ✓ an Error is thrown on navigate in the route 'loader' function 1516ms ✓ 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 1508ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1012ms ✓ an Error is thrown on navigate in the route 'loader' function 1012ms ✓ 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 1006ms ✓ an Error is thrown on navigate in the route 'beforeLoad' function 1510ms ✓ an Error is thrown on navigate in the route 'loader' function 1513ms ✓ 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 1009ms ✓ an Error is thrown on navigate in the route 'loader' function 1011ms ✓ 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 1006ms ✓ @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) ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 3 ⎯⎯⎯⎯⎯⎯⎯ FAIL @tanstack/solid-router tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > async loader, async beforeLoad, pendingMs AssertionError: expected 9 to be 8 // Object.is equality - Expected + Received - 8 + 9 ❯ tests/store-updates-during-navigation.test.tsx:139:21 137| // that needs to be done during a navigation. 138| // Any change that increases this number should be investigated. 139| expect(updates).toBe(8) | ^ 140| }) 141| ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/3]⎯ FAIL @tanstack/solid-router tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > sync beforeLoad AssertionError: expected 5 to be 4 // Object.is equality - Expected + Received - 4 + 5 ❯ tests/store-updates-during-navigation.test.tsx:175:21 173| // Any change that increases this number should be investigated. 174| // Note: Solid has different update counts than React due to diffe… 175| expect(updates).toBe(4) | ^ 176| }) 177| ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/3]⎯ FAIL @tanstack/solid-router tests/store-updates-during-navigation.test.tsx > Store doesn't update *too many* times during navigation > not found in beforeLoad AssertionError: expected 3 to be 4 // Object.is equality - Expected + Received - 4 + 3 ❯ tests/store-updates-during-navigation.test.tsx:201:21 199| // that needs to be done during a navigation. 200| // Any change that increases this number should be investigated. 201| expect(updates).toBe(4) | ^ 202| }) 203| ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/3]⎯ Test Files 1 failed | 44 passed (45) Tests 3 failed | 806 passed | 1 skipped (810) Type Errors no errors Start at 11:57:19 Duration 104.29s (transform 9.67s, setup 5.60s, import 18.63s, tests 91.24s, environment 21.58s, typecheck 20.41s) [ELIFECYCLE] Command failed with exit code 1.