Description

Autocomplete in chromium can trigger a KeyboardEvent where the key property is undefined (as suggested here: https://issues.chromium.org/issues/40539270 and here: microsoft/TypeScript#59631).

In this case, (useMagicKeys/index.ts:122) throws an error:

const depsMapKey = `${key[0].toUpperCase()}${key.slice(1)}`

Additional context

Line :139 (in updateRefs) already suggests that an undefined value is actually anticipated:

const key = e.key?.toLowerCase()

Fixed existing test

While fixing this, I also noticed that the test 'should handle empty key events without errors' probably does not work as intended:

• It does not fail the expect().not.toThrow
• An unhandled error is registered by vitest instead

This is fixed in this PR as well.