Vue - adding bigint to Key broke :key bindings

Describe the bug

The recent change to VirtualItem.Key breaks the :key bindings in v-for loops.

Example:

Your minimal, reproducible example

https://github.com/tanstack/virtual/tree/main/examples/

Steps to reproduce

Setup a virtualizer that uses a key that's not the index e.g.

const rowVirtualizer = useVirtualizer(
  computed(() => {
    return {
      count: props.items.length,
      getScrollElement: () => virtualizerRef.value,
      getItemKey: (index) => props.items[index].id, // <--- id here is string 
      estimateSize: () => 64,
      overscan: 10,
      debug: false,
    };
  })
);

Expected behavior

As a user I expected the :key bindings to not break in Vue v-for loops.

How often does this bug happen?

Every time

Screenshots or Videos

No response

Platform

macOS, Linux

tanstack-virtual version

3.10.6

TypeScript version

5.5.4

Additional context

No response

Terms & Code of Conduct

• I agree to follow this project's Code of Conduct
• I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Start with the Vue examples/ directory and the useVirtualizer setup shown in the report, especially getItemKey when it returns a string id. Reproduce the v-for :key failure with a non-index key, then verify that the bindings remain stable and the relevant example or regression coverage passes.