Svelte error: each_key_duplicate Keyed each block has duplicate key at indexes 0 and 4 in visually-hidden.svelte in select-native.svelte in floating-layer.svelte in select.svelte in SelectTest.svelte ❯ Module.each_key_duplicate ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:111:17 ❯ Module.validate_each_keys ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/validate.js:66:26 ❯ src/lib/bits/select/components/select.svelte:112:31 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:54:12 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:33:90 ❯ execute_reaction_fn ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:375:51 ❯ Module.execute_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:554:18 ❯ create_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:80:26 ❯ Module.branch ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:300:9 ❯ src/lib/bits/select/components/select.svelte:112:31 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "selects item with the { } key". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Svelte error: each_key_duplicate Keyed each block has duplicate key at indexes 0 and 4 in visually-hidden.svelte in select-native.svelte in floating-layer.svelte in select.svelte in SelectTest.svelte ❯ Module.each_key_duplicate ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:111:17 ❯ Module.validate_each_keys ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/validate.js:66:26 ❯ src/lib/bits/select/components/select.svelte:112:31 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:54:12 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:33:90 ❯ execute_reaction_fn ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:375:51 ❯ Module.execute_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:554:18 ❯ create_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:80:26 ❯ Module.branch ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:300:9 ❯ src/lib/bits/select/components/select.svelte:112:31 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "selects item with the {Enter} key". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Svelte error: each_key_duplicate Keyed each block has duplicate key at indexes 0 and 4 in visually-hidden.svelte in select-native.svelte in floating-layer.svelte in select.svelte in SelectTest.svelte ❯ Module.each_key_duplicate ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:111:17 ❯ Module.validate_each_keys ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/validate.js:66:26 ❯ src/lib/bits/select/components/select.svelte:112:31 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:54:12 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:33:90 ❯ execute_reaction_fn ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:375:51 ❯ Module.execute_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:554:18 ❯ create_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:80:26 ❯ Module.branch ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:300:9 ❯ src/lib/bits/select/components/select.svelte:112:31 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "closes on escape keydown". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Svelte error: each_key_duplicate Keyed each block has duplicate key at indexes 0 and 4 in visually-hidden.svelte in select-native.svelte in floating-layer.svelte in select.svelte in SelectTest.svelte ❯ Module.each_key_duplicate ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:111:17 ❯ Module.validate_each_keys ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/validate.js:66:26 ❯ src/lib/bits/select/components/select.svelte:112:31 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:54:12 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:33:90 ❯ execute_reaction_fn ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:375:51 ❯ Module.execute_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:554:18 ❯ create_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:80:26 ❯ Module.branch ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:300:9 ❯ src/lib/bits/select/components/select.svelte:112:31 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "closes on outside click". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Svelte error: each_key_duplicate Keyed each block has duplicate key at indexes 0 and 4 in visually-hidden.svelte in select-native.svelte in floating-layer.svelte in select.svelte in SelectTest.svelte ❯ Module.each_key_duplicate ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:111:17 ❯ Module.validate_each_keys ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/validate.js:66:26 ❯ src/lib/bits/select/components/select.svelte:112:31 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:54:12 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/dom/blocks/snippet.js:33:90 ❯ execute_reaction_fn ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:375:51 ❯ Module.execute_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:554:18 ❯ create_effect ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:80:26 ❯ Module.branch ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/reactivity/effects.js:300:9 ❯ src/lib/bits/select/components/select.svelte:112:31 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "respects binding the `open` prop". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Svelte error: effect_update_depth_exceeded Maximum update depth exceeded. This can happen when a reactive block or effect repeatedly sets a new value. Svelte limits the number of nested updates to prevent infinite loops ❯ Module.effect_update_depth_exceeded ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:181:17 ❯ infinite_loop_guard ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:572:26 ❯ flush_queued_root_effects ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:586:2 ❯ process_deferred ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:650:2 ❯ AsyncResource.runInAsyncScope node:async_hooks:206:9 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "respects binding the `open` prop". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Svelte error: effect_update_depth_exceeded Maximum update depth exceeded. This can happen when a reactive block or effect repeatedly sets a new value. Svelte limits the number of nested updates to prevent infinite loops ❯ Module.effect_update_depth_exceeded ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:181:17 ❯ infinite_loop_guard ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:572:26 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:777:3 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "respects binding the `open` prop". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Svelte error: effect_update_depth_exceeded Maximum update depth exceeded. This can happen when a reactive block or effect repeatedly sets a new value. Svelte limits the number of nested updates to prevent infinite loops ❯ Module.effect_update_depth_exceeded ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:181:17 ❯ infinite_loop_guard ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:572:26 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:777:3 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "respects binding the `open` prop". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Svelte error: effect_update_depth_exceeded Maximum update depth exceeded. This can happen when a reactive block or effect repeatedly sets a new value. Svelte limits the number of nested updates to prevent infinite loops ❯ Module.effect_update_depth_exceeded ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/errors.js:181:17 ❯ infinite_loop_guard ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:572:26 ❯ flush_queued_root_effects ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:586:2 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:787:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 ❯ flush_sync ../../node_modules/.pnpm/[email protected]/node_modules/svelte/src/internal/client/runtime.js:794:4 This error originated in "src/tests/select/Select.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "respects binding the `open` prop". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.