feat(hotkeys): add numpad key support

[MohammedALjaberi]

Summary

Add type-safe support for numpad keys, enabling autocomplete for shortcuts like Mod+Numpad1 or NumpadEnter.

🎯 Changes

• Add NumpadKey type with 16 numpad keys: Numpad0-Numpad9, NumpadAdd, NumpadSubtract, NumpadMultiply, NumpadDivide, NumpadDecimal, NumpadEnter
• Add NUMPAD_KEYS constant set for validation
• Include numpad keys in ALL_KEYS union
• Add NumpadKey to NonPunctuationKey for proper Shift combination typing

Use Cases

• Professional apps (accounting, 3D modeling like Blender)
• Data entry applications
• Gaming shortcuts
• Accessibility (one-handed numpad operation)

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested this code locally with pnpm run test:pr.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
• This change is docs/CI/dev-only (no release).

[pkg-pr-new]

Open in StackBlitz

@tanstack/hotkeys

npm i https://pkg.pr.new/TanStack/hotkeys/@tanstack/hotkeys@28

@tanstack/hotkeys-devtools

npm i https://pkg.pr.new/TanStack/hotkeys/@tanstack/hotkeys-devtools@28

@tanstack/react-hotkeys

npm i https://pkg.pr.new/TanStack/hotkeys/@tanstack/react-hotkeys@28

@tanstack/react-hotkeys-devtools

npm i https://pkg.pr.new/TanStack/hotkeys/@tanstack/react-hotkeys-devtools@28

@tanstack/solid-hotkeys

npm i https://pkg.pr.new/TanStack/hotkeys/@tanstack/solid-hotkeys@28

@tanstack/solid-hotkeys-devtools

npm i https://pkg.pr.new/TanStack/hotkeys/@tanstack/solid-hotkeys-devtools@28

commit: b93986d

[KevinVandy]

So, this is interesting. My original goal was to not support event.code at all and only use event.key. But I guess everyone actually wants to support everything.

[MohammedALjaberi]

So, this is interesting. My original goal was to not support event.code at all and only use event.key. But I guess everyone actually wants to support everything.

@KevinVandy, Given your original design goal of using only event.key, I can close this PR. Let me know if you'd prefer a different approach.

[KevinVandy]

So, this is interesting. My original goal was to not support event.code at all and only use event.key. But I guess everyone actually wants to support everything.

@KevinVandy, Given your original design goal of using only event.key, I can close this PR. Let me know if you'd prefer a different approach.

I'm just actually wondering if we should overhaul the matching system.

[MohammedALjaberi]

So, this is interesting. My original goal was to not support event.code at all and only use event.key. But I guess everyone actually wants to support everything.

@KevinVandy, Given your original design goal of using only event.key, I can close this PR. Let me know if you'd prefer a different approach.

I'm just actually wondering if we should overhaul the matching system.

I appreciate you considering a bigger rethink! aiming for TanStack level quality means building something that truly empowers power users. I’d be excited to see (and help with) a more robust matching system if you decide to go that direction.