Error: useNavigate() may be used only in the context of a <Router> component. ❯ Object.invariant [as UNSAFE_invariant] node_modules/@remix-run/router/history.ts:494:11 ❯ useNavigateUnstable node_modules/react-router/lib/hooks.tsx:188:3 ❯ Proxy.useNavigate node_modules/react-router/lib/hooks.tsx:184:46 ❯ FormLayout src/containers/Form/FormLayout.tsx:233:11 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom.development.js:15486:18 ❯ mountIndeterminateComponent node_modules/react-dom/cjs/react-dom.development.js:20103:13 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:21626:16 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:27465:14 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:26599:12 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:26505:5 This error originated in "src/containers/Search/Search.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should load the search edit". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: useNavigate() may be used only in the context of a <Router> component. ❯ Object.invariant [as UNSAFE_invariant] node_modules/@remix-run/router/history.ts:494:11 ❯ useNavigateUnstable node_modules/react-router/lib/hooks.tsx:188:3 ❯ Proxy.useNavigate node_modules/react-router/lib/hooks.tsx:184:46 ❯ FormLayout src/containers/Form/FormLayout.tsx:233:11 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom.development.js:15486:18 ❯ mountIndeterminateComponent node_modules/react-dom/cjs/react-dom.development.js:20103:13 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:21626:16 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:27465:14 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:26599:12 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:26505:5 This error originated in "src/containers/Search/Search.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "it renders component with saveSearch params". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: useNavigate() may be used only in the context of a <Router> component. ❯ Object.invariant [as UNSAFE_invariant] node_modules/@remix-run/router/history.ts:494:11 ❯ useNavigateUnstable node_modules/react-router/lib/hooks.tsx:188:3 ❯ Proxy.useNavigate node_modules/react-router/lib/hooks.tsx:184:46 ❯ FormLayout src/containers/Form/FormLayout.tsx:233:11 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom.development.js:15486:18 ❯ mountIndeterminateComponent node_modules/react-dom/cjs/react-dom.development.js:20103:13 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:21626:16 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:27465:14 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:26599:12 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:26505:5 This error originated in "src/containers/Profile/Profile.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should render Profile page". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: useNavigate() may be used only in the context of a <Router> component. ❯ Object.invariant [as UNSAFE_invariant] node_modules/@remix-run/router/history.ts:494:11 ❯ useNavigateUnstable node_modules/react-router/lib/hooks.tsx:188:3 ❯ Proxy.useNavigate node_modules/react-router/lib/hooks.tsx:184:46 ❯ FormLayout src/containers/Form/FormLayout.tsx:233:11 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom.development.js:15486:18 ❯ mountIndeterminateComponent node_modules/react-dom/cjs/react-dom.development.js:20103:13 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:21626:16 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:27465:14 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:26599:12 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:26505:5 This error originated in "src/containers/Profile/Profile.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should render profile page for contact profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TestingLibraryElementError: Unable to find an element by: [data-testid="formLayout"] Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/Search/Search.test.tsx:60:9

TestingLibraryElementError: Unable to find an element by: [data-testid="formLayout"] Ignored nodes: comments, script, style <body> <div /> </body> Ignored nodes: comments, script, style <html> <head /> <body> <div /> </body> </html>... ❯ Proxy.waitForWrapper node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ src/containers/Search/Search.test.tsx:83:9

Process completed with exit code 1.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/