xbp → version [NORMAL]
Scope: all 5 workspace projects
? Verifying lockfile against supply-chain policies (709 entries)...
../..                                    | [WARN] Moving @swc/helpers that was installed by a different package manager to "node_modules/.ignored"
../..                                    | [WARN] Moving lefthook that was installed by a different package manager to "node_modules/.ignored"
../..                                    | [WARN] Moving vite that was installed by a different package manager to "node_modules/.ignored"
../..                                    | [WARN] Moving vite-plugin-dts that was installed by a different package manager to "node_modules/.ignored"
../../examples/next-heroui-example       | [WARN] Moving @xylex-group/athena that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @better-auth-ui/react that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @better-auth-ui/core that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @heroui/react that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @heroui/styles that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @xylex-group/athena that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @vitest/browser-playwright that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving playwright that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving vitest that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving shiki that was installed by a different package manager to "node_modules/.ignored"
../..                                    | Progress: resolved 1, reused 0, downloaded 0, added 0
../..                                    | Progress: resolved 60, reused 54, downloaded 0, added 0
../..                                    | Progress: resolved 61, reused 59, downloaded 0, added 0
../..                                    | Progress: resolved 61, reused 60, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (709 entries in 4.1s)
../..                                    | Progress: resolved 62, reused 60, downloaded 0, added 0
../..                                    | Progress: resolved 395, reused 348, downloaded 0, added 0
../..                                    | Progress: resolved 577, reused 484, downloaded 0, added 0
../..                                    | Progress: resolved 905, reused 777, downloaded 0, added 0
[WARN] deprecated @react-email/components@1.0.12: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
../..                                    | Progress: resolved 1044, reused 913, downloaded 0, added 0
../..                                    | Progress: resolved 1121, reused 993, downloaded 0, added 0
[WARN] 21 deprecated subdependencies found: @react-email/body@0.3.0, @react-email/button@0.2.1, @react-email/code-block@0.2.1, @react-email/code-inline@0.0.6, @react-email/column@0.0.14, @react-email/container@0.0.16, @react-email/font@0.0.10, @react-email/head@0.0.13, @react-email/heading@0.0.16, @react-email/hr@0.0.12, @react-email/html@0.0.12, @react-email/img@0.0.12, @react-email/link@0.0.13, @react-email/markdown@0.0.18, @react-email/preview@0.0.14, @react-email/row@0.0.13, @react-email/section@0.0.17, @react-email/tailwind@2.0.7, @react-email/text@0.1.6, uuid@7.0.3, uuid@9.0.1
../..                                    | Progress: resolved 1135, reused 1012, downloaded 0, added 0
../..                                    |  +45   -2 +++++-
../..                                    | Progress: resolved 1135, reused 1013, downloaded 0, added 43
../..                                    | Progress: resolved 1135, reused 1013, downloaded 0, added 45, done
[WARN] The target bin directory already contains an exe called lefthook, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\lefthook.EXE
[WARN] The target bin directory already contains an exe called biome, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\biome.EXE
[WARN] The target bin directory already contains an exe called nx-cloud, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\nx-cloud.EXE
[WARN] The target bin directory already contains an exe called tsc, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\tsc.EXE
[WARN] The target bin directory already contains an exe called nx, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\nx.EXE
[WARN] The target bin directory already contains an exe called vite, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\vite.EXE
[WARN] The target bin directory already contains an exe called tsserver, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\tsserver.EXE
[WARN] The target bin directory already contains an exe called athena-js, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\athena-js.EXE
[WARN] The target bin directory already contains an exe called playwright, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\playwright.EXE
[WARN] The target bin directory already contains an exe called vitest, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\vitest.EXE
[WARN] The target bin directory already contains an exe called expo, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\expo.EXE
[WARN] The target bin directory already contains an exe called tsserver, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\tsserver.EXE
[WARN] The target bin directory already contains an exe called tsc, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\tsc.EXE
[WARN] The target bin directory already contains an exe called expo-modules-autolinking, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\expo-modules-autolinking.EXE
[WARN] The target bin directory already contains an exe called browserslist, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\browserslist.EXE
[WARN] The target bin directory already contains an exe called fingerprint, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\fingerprint.EXE
[WARN] The target bin directory already contains an exe called react-native, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\react-native.EXE
[WARN] The target bin directory already contains an exe called athena-js, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\next-heroui-example\node_modules\.bin\athena-js.EXE
[WARN] The target bin directory already contains an exe called acorn, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\acorn.EXE
[WARN] The target bin directory already contains an exe called baseline-browser-mapping, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\baseline-browser-mapping.EXE
[WARN] The target bin directory already contains an exe called blessed, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\blessed.EXE
[WARN] The target bin directory already contains an exe called detect, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\detect.EXE
[WARN] The target bin directory already contains an exe called detect-port, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\detect-port.EXE
[WARN] The target bin directory already contains an exe called ejs, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\ejs.EXE
[WARN] The target bin directory already contains an exe called flat, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\flat.EXE
[WARN] The target bin directory already contains an exe called is-docker, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\is-docker.EXE
[WARN] The target bin directory already contains an exe called jsesc, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\jsesc.EXE
[WARN] The target bin directory already contains an exe called json5, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\json5.EXE
[WARN] The target bin directory already contains an exe called loose-envify, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\loose-envify.EXE
[WARN] The target bin directory already contains an exe called lz-string, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\lz-string.EXE
[WARN] The target bin directory already contains an exe called marked, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\marked.EXE
[WARN] The target bin directory already contains an exe called nanoid, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\nanoid.EXE
[WARN] The target bin directory already contains an exe called next, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\next.EXE
[WARN] The target bin directory already contains an exe called playwright, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\playwright.EXE
[WARN] The target bin directory already contains an exe called playwright-core, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\playwright-core.EXE
[WARN] The target bin directory already contains an exe called prettier, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\prettier.EXE
[WARN] The target bin directory already contains an exe called regjsparser, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\regjsparser.EXE
[WARN] The target bin directory already contains an exe called resolve, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\resolve.EXE
[WARN] The target bin directory already contains an exe called semver, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\semver.EXE
[WARN] The target bin directory already contains an exe called update-browserslist-db, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\update-browserslist-db.EXE
[WARN] The target bin directory already contains an exe called tree-kill, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\tree-kill.EXE
[WARN] The target bin directory already contains an exe called vitest, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\vitest.EXE
[WARN] The target bin directory already contains an exe called uuid, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\uuid.EXE
[WARN] The target bin directory already contains an exe called why-is-node-running, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\why-is-node-running.EXE
[WARN] The target bin directory already contains an exe called parser, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\parser.EXE
[WARN] The target bin directory already contains an exe called intent, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\intent.EXE
[WARN] The target bin directory already contains an exe called athena-js, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\athena-js.EXE
[WARN] The target bin directory already contains an exe called js-yaml, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\js-yaml.EXE
[WARN] The target bin directory already contains an exe called browserslist, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\browserslist.EXE
[WARN] The target bin directory already contains an exe called jiti, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\jiti.EXE
[WARN] The target bin directory already contains an exe called rolldown, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\rolldown.EXE
[WARN] The target bin directory already contains an exe called yaml, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\yaml.EXE
[WARN] The target bin directory already contains an exe called blessed, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\blessed.EXE
[WARN] The target bin directory already contains an exe called loose-envify, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\loose-envify.EXE
[WARN] The target bin directory already contains an exe called lz-string, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\lz-string.EXE
[WARN] The target bin directory already contains an exe called marked, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\marked.EXE
[WARN] The target bin directory already contains an exe called nanoid, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\nanoid.EXE
[WARN] The target bin directory already contains an exe called playwright-core, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\playwright-core.EXE
[WARN] The target bin directory already contains an exe called prettier, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\prettier.EXE
[WARN] The target bin directory already contains an exe called rolldown, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\rolldown.EXE
[WARN] The target bin directory already contains an exe called uuid, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\uuid.EXE
[WARN] The target bin directory already contains an exe called intent, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\intent.EXE
[WARN] The target bin directory already contains an exe called why-is-node-running, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\why-is-node-running.EXE
[WARN] The target bin directory already contains an exe called vite, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\vite.EXE
[WARN] The target bin directory already contains an exe called eslint, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\eslint.EXE
[WARN] The target bin directory already contains an exe called napi-postinstall, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\napi-postinstall.EXE
[WARN] The target bin directory already contains an exe called expo-internal, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\expo-internal.EXE
[WARN] Issues with peer dependencies found. Run "pnpm peers check" to list them.

dependencies:
+ shiki 4.2.0

devDependencies:
- @xylex-group/athena
+ @xylex-group/athena 2.8.0 (2.8.2 is available)

Done in 14.5s using pnpm v11.8.0
$ vitest

 RUN  v4.1.8 C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui

5:07:20 PM [vite] (client) Re-optimizing dependencies because lockfile has changed
5:07:21 PM [vite] (client) [optimizer] scanning dependencies...
(!) Failed to run dependency scan. Skipping dependency pre-bundling. Error: The following dependencies are imported but could not be resolved:

  @/lib/auth/ui-options (imported by C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx)

Are they installed?
    at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:31628:33
    at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:23353:15
5:07:23 PM [vite] (client) Pre-transform error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
5:07:23 PM [vite] Internal server error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
      at TransformPluginContext._formatLog (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30602:39)
      at TransformPluginContext.error (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30599:14)
      at normalizeUrl (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27842:18)
      at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27905:30
      at async Promise.all (index 3)
      at TransformPluginContext.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27873:4)
      at EnvironmentPluginContainer.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30387:14)
      at loadAndTransform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24646:26)
 ❯ |chromium| tests/auth-routes.test.ts (0 test)
5:07:23 PM [vite] (client) Pre-transform error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
5:07:24 PM [vite] (client) [optimizer] bundling dependencies...
 ✓ |chromium| tests/auth-routing-debug.test.ts (2 tests) 2ms
5:07:27 PM [vite] (client) [optimizer] bundling dependencies...
5:07:29 PM [vite] (client) ✨ new dependencies optimized: @better-auth-ui/core, @better-auth-ui/core/plugins, @better-auth-ui/react, @better-auth-ui/react/email, @gravity-ui/icons, @heroui/react, @heroui/styles, @internationalized/date, @tanstack/react-pacer, @tanstack/react-query, @testing-library/react, @xylex-group/athena/browser, bowser, shiki

[vitest] Vite unexpectedly reloaded a test. This may cause tests to fail, lead to flaky behaviour or duplicated test runs.
For a stable experience, please add mentioned dependencies to your config's `optimizeDeps.include` field manually.


5:07:29 PM [vite] (client) ✨ optimized dependencies changed. reloading
 ❯ |chromium| tests/change-password.test.tsx (0 test)
5:07:32 PM [vite] (client) [optimizer] bundling dependencies...
5:07:36 PM [vite] (client) ✨ new dependencies optimized: @testing-library/user-event

[vitest] Vite unexpectedly reloaded a test. This may cause tests to fail, lead to flaky behaviour or duplicated test runs.
For a stable experience, please add mentioned dependencies to your config's `optimizeDeps.include` field manually.


5:07:36 PM [vite] (client) ✨ optimized dependencies changed. reloading
stderr | tests/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

a ✓ |chromium| tests/passkeys.test.tsx (14 tests) 752ms
ct(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to Passkey inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to Passkey inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
 ❯ |chromium| tests/settings-sections.test.tsx (3 tests | 1 failed) 44ms
     × can select and reorder account sections 33ms
     ✓ can select and reorder security sections 4ms
     ✓ can select and reorder workspace sections 3ms
 ✓ |chromium| tests/username.test.tsx (15 tests) 4368ms
     ✓ does not re-request conditional passkey autofill while typing  483ms
     ✓ shows the 'available' indicator after typing a free username  586ms
     ✓ shows the 'taken' indicator when the username is unavailable  579ms
     ✓ does not call isUsernameAvailable when the option is disabled  790ms
     ✓ skips the availability check when the value matches the user's current username  1275ms
 ✓ |chromium| tests/email.test.tsx (1 test) 1058ms
     ✓ exports the email template catalog and bound template metadata  1058ms
 ✓ |chromium| tests/sign-up.test.tsx (2 tests) 784ms
     ✓ navigates to the check-email view when verification is required  400ms
     ✓ uses the check-email route override when provided  384ms
 ✓ |chromium| tests/forgot-password.test.tsx (5 tests) 694ms
5:07:48 PM [vite] Internal server error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
      at TransformPluginContext._formatLog (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30602:39)
      at TransformPluginContext.error (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30599:14)
      at normalizeUrl (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27842:18)
      at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27905:30
      at async Promise.all (index 3)
      at TransformPluginContext.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27873:4)
      at EnvironmentPluginContainer.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30387:14)
      at loadAndTransform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24646:26)
 ❯ |chromium| tests/integration.test.tsx (4 tests | 4 failed) 248ms
5:07:48 PM [vite] (client) Pre-transform error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
     × should export main components 245ms
     × should have all main components as functions 2ms
     × should export plugin components and factories 1ms
     × should have all plugin exports as functions 0ms
5:07:48 PM [vite] (client) Pre-transform error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
 ✓ |chromium| tests/sign-in.test.tsx (9 tests) 504ms
     ✓ does not re-request conditional passkey autofill while typing  364ms
 ✓ |chromium| tests/magic-link.test.tsx (2 tests) 386ms
 ✓ |chromium| tests/reset-password.test.tsx (2 tests) 283ms
 ✓ |chromium| tests/auth-routing-debug-overlay.test.tsx (3 tests) 112ms
 ✓ |chromium| tests/change-email.test.tsx (1 test) 164ms
 ✓ |chromium| tests/auth-router.test.tsx (4 tests) 34ms
 ✓ |chromium| tests/theme-switcher.test.tsx (2 tests) 44ms
stderr | tests/theme-switcher.test.tsx:26:3 > <ThemeSwitcher /> > renders only the available themes as tabs and selects the active one
An update to ForwardRef(SharedElement) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
 ✓ |chromium| tests/api-keys.test.tsx (2 tests) 33ms
 ✓ |chromium| tests/linked-accounts.test.tsx (3 tests) 28ms
 ❯ |chromium| tests/settings.test.tsx (0 test)
5:07:53 PM [vite] Internal server error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
      at TransformPluginContext._formatLog (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30602:39)
      at TransformPluginContext.error (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30599:14)
      at normalizeUrl (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27842:18)
      at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27905:30
      at async Promise.all (index 3)
      at TransformPluginContext.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27873:4)
      at EnvironmentPluginContainer.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30387:14)
      at loadAndTransform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24646:26)
      at viteTransformMiddleware (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24440:20)
 ✓ |chromium| tests/sign-out.test.tsx (2 tests) 8ms
 ✓ |chromium| tests/deduped-error-toast.test.ts (3 tests) 2ms
 ✓ |chromium| tests/athena-client.test.ts (2 tests) 3ms
 ✓ |chromium| tests/client-url.test.ts (2 tests) 1ms
 ✓ |chromium| tests/social-redirect.test.ts (4 tests) 1ms
 ❯ |chromium| tests/base-url.test.ts (0 test)
5:07:54 PM [vite] Internal server error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
      at TransformPluginContext._formatLog (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30602:39)
      at TransformPluginContext.error (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30599:14)
      at normalizeUrl (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27842:18)
      at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27905:30
      at async Promise.all (index 3)
      at TransformPluginContext.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27873:4)
      at EnvironmentPluginContainer.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30387:14)
      at loadAndTransform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24646:26)
      at viteTransformMiddleware (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24440:20)


⎯⎯⎯⎯⎯⎯ Failed Suites 4 ⎯⎯⎯⎯⎯⎯⎯

 Test Files  6 failed | 20 passed (26)
      Tests  5 failed | 82 passed (87)
   Start at  17:07:20
   Duration  34.31s (transform 0ms, setup 0ms, import 10.58s, tests 9.55s, environment 0ms)

 FAIL  |chromium| tests/auth-routes.test.ts [ tests/auth-routes.test.ts ]
Error: Failed to import test file C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/auth-routes.test.ts
Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:63315/@fs/C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/auth-routes.test.ts?import&browserv=1781968042812
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/9]⎯

 FAIL  |chromium| tests/base-url.test.ts [ tests/base-url.test.ts ]
Error: Failed to import test file C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/base-url.test.ts
Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:63315/@fs/C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/base-url.test.ts?import&browserv=1781968074637
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/9]⎯

 FAIL  |chromium| tests/change-password.test.tsx [ tests/change-password.test.tsx ]
Error: Failed to import test file C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/change-password.test.tsx
Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:63315/node_modules/.vite/vitest/da39a3ee5e6b4b0d3255bfef95601890afd80709/deps/react_jsx-dev-runtime.js?v=884544d3
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/9]⎯

 FAIL  |chromium| tests/settings.test.tsx [ tests/settings.test.tsx ]
Error: Failed to import test file C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/settings.test.tsx
Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:63315/src/components/auth/settings/settings.tsx
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/9]⎯


⎯⎯⎯⎯⎯⎯⎯ Failed Tests 5 ⎯⎯⎯⎯⎯⎯⎯

 FAIL  |chromium| tests/integration.test.tsx:42:3 > @xylex-group/athena-auth-ui integration > should export main components
 FAIL  |chromium| tests/integration.test.tsx:50:3 > @xylex-group/athena-auth-ui integration > should have all main components as functions
 FAIL  |chromium| tests/integration.test.tsx:58:3 > @xylex-group/athena-auth-ui integration > should export plugin components and factories
 FAIL  |chromium| tests/integration.test.tsx:66:3 > @xylex-group/athena-auth-ui integration > should have all plugin exports as functions
TypeError: Failed to fetch dynamically imported module: http://localhost:63315/src/index.ts
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[5/9]⎯

 FAIL  |chromium| tests/settings-sections.test.tsx:157:3 > settings section configuration > can select and reorder account sections
AssertionError: expected [ 'account-plugin', …(3) ] to deeply equal [ 'account-plugin', …(2) ]

- Expected
+ Received

  [
    "account-plugin",
    "account-changeEmail",
    "account-organizationDangerZone",
+   "account-deleteUser",
  ]

 ❯ tests/settings-sections.test.tsx:175:6
    173|     expect(
    174|       screen.getAllByTestId(/^account-/).map((node) => node.dataset.te…
    175|     ).toEqual([
       |      ^
    176|       "account-plugin",
    177|       "account-changeEmail",

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[6/9]⎯

[ELIFECYCLE] Test failed. See above for more details.
[OPERATION] version
  release version failed
  Details: Preflight command failed for @xylex-group/athena-auth-ui: `pnpm test`
stdout:
Scope: all 5 workspace projects
? Verifying lockfile against supply-chain policies (709 entries)...
../..                                    | [WARN] Moving @swc/helpers that was installed by a different package manager to "node_modules/.ignored"
../..                                    | [WARN] Moving lefthook that was installed by a different package manager to "node_modules/.ignored"
../..                                    | [WARN] Moving vite that was installed by a different package manager to "node_modules/.ignored"
../..                                    | [WARN] Moving vite-plugin-dts that was installed by a different package manager to "node_modules/.ignored"
../../examples/next-heroui-example       | [WARN] Moving @xylex-group/athena that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @better-auth-ui/react that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @better-auth-ui/core that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @heroui/react that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @heroui/styles that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @xylex-group/athena that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving @vitest/browser-playwright that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving playwright that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving vitest that was installed by a different package manager to "node_modules/.ignored"
../heroui-native                         | [WARN] Moving shiki that was installed by a different package manager to "node_modules/.ignored"
../..                                    | Progress: resolved 1, reused 0, downloaded 0, added 0
../..                                    | Progress: resolved 60, reused 54, downloaded 0, added 0
../..                                    | Progress: resolved 61, reused 59, downloaded 0, added 0
../..                                    | Progress: resolved 61, reused 60, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (709 entries in 4.1s)
../..                                    | Progress: resolved 62, reused 60, downloaded 0, added 0
../..                                    | Progress: resolved 395, reused 348, downloaded 0, added 0
../..                                    | Progress: resolved 577, reused 484, downloaded 0, added 0
../..                                    | Progress: resolved 905, reused 777, downloaded 0, added 0
[WARN] deprecated @react-email/components@1.0.12: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
../..                                    | Progress: resolved 1044, reused 913, downloaded 0, added 0
../..                                    | Progress: resolved 1121, reused 993, downloaded 0, added 0
[WARN] 21 deprecated subdependencies found: @react-email/body@0.3.0, @react-email/button@0.2.1, @react-email/code-block@0.2.1, @react-email/code-inline@0.0.6, @react-email/column@0.0.14, @react-email/container@0.0.16, @react-email/font@0.0.10, @react-email/head@0.0.13, @react-email/heading@0.0.16, @react-email/hr@0.0.12, @react-email/html@0.0.12, @react-email/img@0.0.12, @react-email/link@0.0.13, @react-email/markdown@0.0.18, @react-email/preview@0.0.14, @react-email/row@0.0.13, @react-email/section@0.0.17, @react-email/tailwind@2.0.7, @react-email/text@0.1.6, uuid@7.0.3, uuid@9.0.1
../..                                    | Progress: resolved 1135, reused 1012, downloaded 0, added 0
../..                                    |  +45   -2 +++++-
../..                                    | Progress: resolved 1135, reused 1013, downloaded 0, added 43
../..                                    | Progress: resolved 1135, reused 1013, downloaded 0, added 45, done
[WARN] The target bin directory already contains an exe called lefthook, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\lefthook.EXE
[WARN] The target bin directory already contains an exe called biome, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\biome.EXE
[WARN] The target bin directory already contains an exe called nx-cloud, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\nx-cloud.EXE
[WARN] The target bin directory already contains an exe called tsc, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\tsc.EXE
[WARN] The target bin directory already contains an exe called nx, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\nx.EXE
[WARN] The target bin directory already contains an exe called vite, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\vite.EXE
[WARN] The target bin directory already contains an exe called tsserver, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\tsserver.EXE
[WARN] The target bin directory already contains an exe called athena-js, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\athena-js.EXE
[WARN] The target bin directory already contains an exe called playwright, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\playwright.EXE
[WARN] The target bin directory already contains an exe called vitest, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\vitest.EXE
[WARN] The target bin directory already contains an exe called expo, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\expo.EXE
[WARN] The target bin directory already contains an exe called tsserver, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\tsserver.EXE
[WARN] The target bin directory already contains an exe called tsc, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\tsc.EXE
[WARN] The target bin directory already contains an exe called expo-modules-autolinking, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\expo-modules-autolinking.EXE
[WARN] The target bin directory already contains an exe called browserslist, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\browserslist.EXE
[WARN] The target bin directory already contains an exe called fingerprint, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\fingerprint.EXE
[WARN] The target bin directory already contains an exe called react-native, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\react-native.EXE
[WARN] The target bin directory already contains an exe called athena-js, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\next-heroui-example\node_modules\.bin\athena-js.EXE
[WARN] The target bin directory already contains an exe called acorn, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\acorn.EXE
[WARN] The target bin directory already contains an exe called baseline-browser-mapping, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\baseline-browser-mapping.EXE
[WARN] The target bin directory already contains an exe called blessed, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\blessed.EXE
[WARN] The target bin directory already contains an exe called detect, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\detect.EXE
[WARN] The target bin directory already contains an exe called detect-port, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\detect-port.EXE
[WARN] The target bin directory already contains an exe called ejs, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\ejs.EXE
[WARN] The target bin directory already contains an exe called flat, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\flat.EXE
[WARN] The target bin directory already contains an exe called is-docker, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\is-docker.EXE
[WARN] The target bin directory already contains an exe called jsesc, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\jsesc.EXE
[WARN] The target bin directory already contains an exe called json5, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\json5.EXE
[WARN] The target bin directory already contains an exe called loose-envify, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\loose-envify.EXE
[WARN] The target bin directory already contains an exe called lz-string, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\lz-string.EXE
[WARN] The target bin directory already contains an exe called marked, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\marked.EXE
[WARN] The target bin directory already contains an exe called nanoid, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\nanoid.EXE
[WARN] The target bin directory already contains an exe called next, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\next.EXE
[WARN] The target bin directory already contains an exe called playwright, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\playwright.EXE
[WARN] The target bin directory already contains an exe called playwright-core, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\playwright-core.EXE
[WARN] The target bin directory already contains an exe called prettier, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\prettier.EXE
[WARN] The target bin directory already contains an exe called regjsparser, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\regjsparser.EXE
[WARN] The target bin directory already contains an exe called resolve, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\resolve.EXE
[WARN] The target bin directory already contains an exe called semver, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\semver.EXE
[WARN] The target bin directory already contains an exe called update-browserslist-db, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\update-browserslist-db.EXE
[WARN] The target bin directory already contains an exe called tree-kill, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\tree-kill.EXE
[WARN] The target bin directory already contains an exe called vitest, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\vitest.EXE
[WARN] The target bin directory already contains an exe called uuid, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\uuid.EXE
[WARN] The target bin directory already contains an exe called why-is-node-running, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\why-is-node-running.EXE
[WARN] The target bin directory already contains an exe called parser, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\parser.EXE
[WARN] The target bin directory already contains an exe called intent, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\intent.EXE
[WARN] The target bin directory already contains an exe called athena-js, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\athena-js.EXE
[WARN] The target bin directory already contains an exe called js-yaml, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\js-yaml.EXE
[WARN] The target bin directory already contains an exe called browserslist, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\browserslist.EXE
[WARN] The target bin directory already contains an exe called jiti, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\jiti.EXE
[WARN] The target bin directory already contains an exe called rolldown, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\rolldown.EXE
[WARN] The target bin directory already contains an exe called yaml, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\node_modules\.bin\yaml.EXE
[WARN] The target bin directory already contains an exe called blessed, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\blessed.EXE
[WARN] The target bin directory already contains an exe called loose-envify, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\loose-envify.EXE
[WARN] The target bin directory already contains an exe called lz-string, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\lz-string.EXE
[WARN] The target bin directory already contains an exe called marked, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\marked.EXE
[WARN] The target bin directory already contains an exe called nanoid, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\nanoid.EXE
[WARN] The target bin directory already contains an exe called playwright-core, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\playwright-core.EXE
[WARN] The target bin directory already contains an exe called prettier, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\prettier.EXE
[WARN] The target bin directory already contains an exe called rolldown, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\rolldown.EXE
[WARN] The target bin directory already contains an exe called uuid, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\uuid.EXE
[WARN] The target bin directory already contains an exe called intent, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\intent.EXE
[WARN] The target bin directory already contains an exe called why-is-node-running, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\why-is-node-running.EXE
[WARN] The target bin directory already contains an exe called vite, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\packages\heroui-native\node_modules\.bin\vite.EXE
[WARN] The target bin directory already contains an exe called eslint, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\eslint.EXE
[WARN] The target bin directory already contains an exe called napi-postinstall, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\napi-postinstall.EXE
[WARN] The target bin directory already contains an exe called expo-internal, so removing C:\Users\floris\Documents\GitHub\athena-auth-ui\examples\native-heroui-example\node_modules\.bin\expo-internal.EXE
[WARN] Issues with peer dependencies found. Run "pnpm peers check" to list them.

dependencies:
+ shiki 4.2.0

devDependencies:
- @xylex-group/athena
+ @xylex-group/athena 2.8.0 (2.8.2 is available)

Done in 14.5s using pnpm v11.8.0

 RUN  v4.1.8 C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui

5:07:20 PM [vite] (client) Re-optimizing dependencies because lockfile has changed
5:07:21 PM [vite] (client) [optimizer] scanning dependencies...
 ❯ |chromium| tests/auth-routes.test.ts (0 test)
5:07:24 PM [vite] (client) [optimizer] bundling dependencies...
 ✓ |chromium| tests/auth-routing-debug.test.ts (2 tests) 2ms
5:07:27 PM [vite] (client) [optimizer] bundling dependencies...
5:07:29 PM [vite] (client) ✨ new dependencies optimized: @better-auth-ui/core, @better-auth-ui/core/plugins, @better-auth-ui/react, @better-auth-ui/react/email, @gravity-ui/icons, @heroui/react, @heroui/styles, @internationalized/date, @tanstack/react-pacer, @tanstack/react-query, @testing-library/react, @xylex-group/athena/browser, bowser, shiki
5:07:29 PM [vite] (client) ✨ optimized dependencies changed. reloading
 ❯ |chromium| tests/change-password.test.tsx (0 test)
5:07:32 PM [vite] (client) [optimizer] bundling dependencies...
5:07:36 PM [vite] (client) ✨ new dependencies optimized: @testing-library/user-event
5:07:36 PM [vite] (client) ✨ optimized dependencies changed. reloading
 ✓ |chromium| tests/passkeys.test.tsx (14 tests) 752ms
 ❯ |chromium| tests/settings-sections.test.tsx (3 tests | 1 failed) 44ms
     × can select and reorder account sections 33ms
     ✓ can select and reorder security sections 4ms
     ✓ can select and reorder workspace sections 3ms
 ✓ |chromium| tests/username.test.tsx (15 tests) 4368ms
     ✓ does not re-request conditional passkey autofill while typing  483ms
     ✓ shows the 'available' indicator after typing a free username  586ms
     ✓ shows the 'taken' indicator when the username is unavailable  579ms
     ✓ does not call isUsernameAvailable when the option is disabled  790ms
     ✓ skips the availability check when the value matches the user's current username  1275ms
 ✓ |chromium| tests/email.test.tsx (1 test) 1058ms
     ✓ exports the email template catalog and bound template metadata  1058ms
 ✓ |chromium| tests/sign-up.test.tsx (2 tests) 784ms
     ✓ navigates to the check-email view when verification is required  400ms
     ✓ uses the check-email route override when provided  384ms
 ✓ |chromium| tests/forgot-password.test.tsx (5 tests) 694ms
 ❯ |chromium| tests/integration.test.tsx (4 tests | 4 failed) 248ms
     × should export main components 245ms
     × should have all main components as functions 2ms
     × should export plugin components and factories 1ms
     × should have all plugin exports as functions 0ms
 ✓ |chromium| tests/sign-in.test.tsx (9 tests) 504ms
     ✓ does not re-request conditional passkey autofill while typing  364ms
 ✓ |chromium| tests/magic-link.test.tsx (2 tests) 386ms
 ✓ |chromium| tests/reset-password.test.tsx (2 tests) 283ms
 ✓ |chromium| tests/auth-routing-debug-overlay.test.tsx (3 tests) 112ms
 ✓ |chromium| tests/change-email.test.tsx (1 test) 164ms
 ✓ |chromium| tests/auth-router.test.tsx (4 tests) 34ms
 ✓ |chromium| tests/theme-switcher.test.tsx (2 tests) 44ms
 ✓ |chromium| tests/api-keys.test.tsx (2 tests) 33ms
 ✓ |chromium| tests/linked-accounts.test.tsx (3 tests) 28ms
 ❯ |chromium| tests/settings.test.tsx (0 test)
 ✓ |chromium| tests/sign-out.test.tsx (2 tests) 8ms
 ✓ |chromium| tests/deduped-error-toast.test.ts (3 tests) 2ms
 ✓ |chromium| tests/athena-client.test.ts (2 tests) 3ms
 ✓ |chromium| tests/client-url.test.ts (2 tests) 1ms
 ✓ |chromium| tests/social-redirect.test.ts (4 tests) 1ms
 ❯ |chromium| tests/base-url.test.ts (0 test)

 Test Files  6 failed | 20 passed (26)
      Tests  5 failed | 82 passed (87)
   Start at  17:07:20
   Duration  34.31s (transform 0ms, setup 0ms, import 10.58s, tests 9.55s, environment 0ms)

[ELIFECYCLE] Test failed. See above for more details.

stderr:
$ vitest
(!) Failed to run dependency scan. Skipping dependency pre-bundling. Error: The following dependencies are imported but could not be resolved:

  @/lib/auth/ui-options (imported by C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx)

Are they installed?
    at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:31628:33
    at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:23353:15
5:07:23 PM [vite] (client) Pre-transform error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
5:07:23 PM [vite] Internal server error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
      at TransformPluginContext._formatLog (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30602:39)
      at TransformPluginContext.error (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30599:14)
      at normalizeUrl (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27842:18)
      at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27905:30
      at async Promise.all (index 3)
      at TransformPluginContext.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27873:4)
      at EnvironmentPluginContainer.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30387:14)
      at loadAndTransform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24646:26)
5:07:23 PM [vite] (client) Pre-transform error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";

[vitest] Vite unexpectedly reloaded a test. This may cause tests to fail, lead to flaky behaviour or duplicated test runs.
For a stable experience, please add mentioned dependencies to your config's `optimizeDeps.include` field manually.



[vitest] Vite unexpectedly reloaded a test. This may cause tests to fail, lead to flaky behaviour or duplicated test runs.
For a stable experience, please add mentioned dependencies to your config's `optimizeDeps.include` field manually.


stderr | tests/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:75:2 > <PasskeyButton /> > calls authClient.signIn.passkey on click
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:102:2 > <PasskeyButton /> > ignores dismissed passkey sign-in prompts
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:117:2 > <PasskeyButton /> > does not toast when passkey sign-in fails on the login surface
An update to PasskeyButton inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:210:2 > <Passkeys /> > opens the name dialog when the add button is clicked
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:219:2 > <Passkeys /> > calls addPasskey when the dialog is submitted without a name
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:237:2 > <Passkeys /> > forwards the typed name to addPasskey
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to Passkeys inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Input) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:256:2 > <Passkeys /> > ignores dismissed add-passkey prompts
An update to AddPasskeyDialog inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to Passkey inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to $d7a937236970dc7f$export$c6fdb837b070b4ff inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to $8b8d26808cb8cb53$var$ModalContent inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to $8b8d26808cb8cb53$var$ModalOverlayInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to Passkey inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef($8b8d26808cb8cb53$var$ModalOverlayWithForwardRef) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(TextField) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures 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/passkeys.test.tsx:291:2 > <Passkeys /> > calls deletePasskey with the correct id
An update to ForwardRef(Button) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
5:07:48 PM [vite] Internal server error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
      at TransformPluginContext._formatLog (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30602:39)
      at TransformPluginContext.error (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30599:14)
      at normalizeUrl (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27842:18)
      at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27905:30
      at async Promise.all (index 3)
      at TransformPluginContext.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27873:4)
      at EnvironmentPluginContainer.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30387:14)
      at loadAndTransform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24646:26)
5:07:48 PM [vite] (client) Pre-transform error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
5:07:48 PM [vite] (client) Pre-transform error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
stderr | tests/theme-switcher.test.tsx:26:3 > <ThemeSwitcher /> > renders only the available themes as tabs and selects the active one
An update to ForwardRef(SharedElement) inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
5:07:53 PM [vite] Internal server error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
      at TransformPluginContext._formatLog (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30602:39)
      at TransformPluginContext.error (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30599:14)
      at normalizeUrl (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27842:18)
      at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27905:30
      at async Promise.all (index 3)
      at TransformPluginContext.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27873:4)
      at EnvironmentPluginContainer.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30387:14)
      at loadAndTransform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24646:26)
      at viteTransformMiddleware (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24440:20)
5:07:54 PM [vite] Internal server error: Failed to resolve import "@/lib/auth/ui-options" from "src/components/auth/settings/settings.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/src/components/auth/settings/settings.tsx:12:7
  2  |  import { Button, cn, Link } from "@heroui/react";
  3  |  import { useEffect, useMemo, useState } from "react";
  4  |  import { AuthUiProvider, getAuthUiRoute, useResolvedAuthUiOptions } from "@/lib/auth/ui-options";
     |                                                                            ^
  5  |  import { AccountSettings } from "./account/account-settings";
  6  |  import { SecuritySettings } from "./security/security-settings";
      at TransformPluginContext._formatLog (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30602:39)
      at TransformPluginContext.error (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30599:14)
      at normalizeUrl (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27842:18)
      at file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27905:30
      at async Promise.all (index 3)
      at TransformPluginContext.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:27873:4)
      at EnvironmentPluginContainer.transform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:30387:14)
      at loadAndTransform (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24646:26)
      at viteTransformMiddleware (file:///C:/Users/floris/Documents/GitHub/athena-auth-ui/node_modules/.pnpm/vite@8.0.16_@types+node@25._250abadfcefeaea47ac7b25feee83ca3/node_modules/vite/dist/node/chunks/node.js:24440:20)

⎯⎯⎯⎯⎯⎯ Failed Suites 4 ⎯⎯⎯⎯⎯⎯⎯

 FAIL  |chromium| tests/auth-routes.test.ts [ tests/auth-routes.test.ts ]
Error: Failed to import test file C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/auth-routes.test.ts
Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:63315/@fs/C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/auth-routes.test.ts?import&browserv=1781968042812
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/9]⎯

 FAIL  |chromium| tests/base-url.test.ts [ tests/base-url.test.ts ]
Error: Failed to import test file C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/base-url.test.ts
Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:63315/@fs/C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/base-url.test.ts?import&browserv=1781968074637
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/9]⎯

 FAIL  |chromium| tests/change-password.test.tsx [ tests/change-password.test.tsx ]
Error: Failed to import test file C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/change-password.test.tsx
Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:63315/node_modules/.vite/vitest/da39a3ee5e6b4b0d3255bfef95601890afd80709/deps/react_jsx-dev-runtime.js?v=884544d3
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/9]⎯

 FAIL  |chromium| tests/settings.test.tsx [ tests/settings.test.tsx ]
Error: Failed to import test file C:/Users/floris/Documents/GitHub/athena-auth-ui/packages/heroui/tests/settings.test.tsx
Caused by: TypeError: Failed to fetch dynamically imported module: http://localhost:63315/src/components/auth/settings/settings.tsx
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/9]⎯


⎯⎯⎯⎯⎯⎯⎯ Failed Tests 5 ⎯⎯⎯⎯⎯⎯⎯

 FAIL  |chromium| tests/integration.test.tsx:42:3 > @xylex-group/athena-auth-ui integration > should export main components
 FAIL  |chromium| tests/integration.test.tsx:50:3 > @xylex-group/athena-auth-ui integration > should have all main components as functions
 FAIL  |chromium| tests/integration.test.tsx:58:3 > @xylex-group/athena-auth-ui integration > should export plugin components and factories
 FAIL  |chromium| tests/integration.test.tsx:66:3 > @xylex-group/athena-auth-ui integration > should have all plugin exports as functions
TypeError: Failed to fetch dynamically imported module: http://localhost:63315/src/index.ts
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[5/9]⎯

 FAIL  |chromium| tests/settings-sections.test.tsx:157:3 > settings section configuration > can select and reorder account sections
AssertionError: expected [ 'account-plugin', …(3) ] to deeply equal [ 'account-plugin', …(2) ]

- Expected
+ Received

  [
    "account-plugin",
    "account-changeEmail",
    "account-organizationDangerZone",
+   "account-deleteUser",
  ]

 ❯ tests/settings-sections.test.tsx:175:6
    173|     expect(
    174|       screen.getAllByTestId(/^account-/).map((node) => node.dataset.te…
    175|     ).toEqual([
       |      ^
    176|       "account-plugin",
    177|       "account-changeEmail",

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[6/9]⎯
  Hint: Use `--allow-dirty` if only generated files changed.
