Skip to content

ci: Version Packages - #212

Merged
KevinVandy merged 1 commit into
mainfrom
changeset-release/main
Oct 30, 2026
Merged

ci: Version Packages#212
KevinVandy merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@tanstack/alpine-hotkeys@0.8.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

Patch Changes

@tanstack/angular-hotkeys@0.18.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

  • #211 8b93ed5 - Providers no longer bundle app hotkey support unless the app uses defineAppHotkeys. A React app with HotkeysProvider and no app hotkeys is about 1 kB smaller (brotli).

Patch Changes

@tanstack/angular-hotkeys-devtools@0.4.0

Minor Changes

  • #211 8b93ed5 - Each devtools adapter now lists its TanStack Devtools host as an optional peer dependency at the current release, such as @tanstack/react-devtools 0.10.14. Older hosts pass the plugin a theme string instead of props, so the panel ignored the theme, and TypeScript rejects the React plugin since @tanstack/react-hotkeys-devtools 0.12.0. Package managers now warn about an old host at install time.

    Update @tanstack/devtools-utils and @tanstack/devtools-ui to 0.7.2. The Preact panel now unmounts its core on Preact 11 (fix(preact): Unmount panels on Preact 11 and pass app context to plugins devtools#551).

Patch Changes

  • Updated dependencies [8b93ed5, 8b93ed5]:
    • @tanstack/hotkeys-devtools@1.7.0

@tanstack/ember-hotkeys@0.7.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

Patch Changes

@tanstack/hotkeys@0.20.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - Console warnings and errors are logged only in development. Production builds, where process.env.NODE_ENV is 'production', skip them and drop the warning code. checkHotkey still returns whether a hotkey is valid.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

  • #211 8b93ed5 - Providers no longer bundle app hotkey support unless the app uses defineAppHotkeys. A React app with HotkeysProvider and no app hotkeys is about 1 kB smaller (brotli).

@tanstack/hotkeys-devtools@1.7.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - Each devtools adapter now lists its TanStack Devtools host as an optional peer dependency at the current release, such as @tanstack/react-devtools 0.10.14. Older hosts pass the plugin a theme string instead of props, so the panel ignored the theme, and TypeScript rejects the React plugin since @tanstack/react-hotkeys-devtools 0.12.0. Package managers now warn about an old host at install time.

    Update @tanstack/devtools-utils and @tanstack/devtools-ui to 0.7.2. The Preact panel now unmounts its core on Preact 11 (fix(preact): Unmount panels on Preact 11 and pass app context to plugins devtools#551).

Patch Changes

@tanstack/lit-hotkeys@0.19.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

Patch Changes

@tanstack/octane-hotkeys@0.8.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

  • #211 8b93ed5 - Providers no longer bundle app hotkey support unless the app uses defineAppHotkeys. A React app with HotkeysProvider and no app hotkeys is about 1 kB smaller (brotli).

Patch Changes

@tanstack/preact-hotkeys@0.18.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

  • #211 8b93ed5 - Providers no longer bundle app hotkey support unless the app uses defineAppHotkeys. A React app with HotkeysProvider and no app hotkeys is about 1 kB smaller (brotli).

Patch Changes

@tanstack/preact-hotkeys-devtools@0.12.0

Minor Changes

  • #211 8b93ed5 - Each devtools adapter now lists its TanStack Devtools host as an optional peer dependency at the current release, such as @tanstack/react-devtools 0.10.14. Older hosts pass the plugin a theme string instead of props, so the panel ignored the theme, and TypeScript rejects the React plugin since @tanstack/react-hotkeys-devtools 0.12.0. Package managers now warn about an old host at install time.

    Update @tanstack/devtools-utils and @tanstack/devtools-ui to 0.7.2. The Preact panel now unmounts its core on Preact 11 (fix(preact): Unmount panels on Preact 11 and pass app context to plugins devtools#551).

Patch Changes

  • Updated dependencies [8b93ed5, 8b93ed5]:
    • @tanstack/hotkeys-devtools@1.7.0

@tanstack/react-hotkeys@0.19.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

  • #211 8b93ed5 - Providers no longer bundle app hotkey support unless the app uses defineAppHotkeys. A React app with HotkeysProvider and no app hotkeys is about 1 kB smaller (brotli).

Patch Changes

@tanstack/react-hotkeys-devtools@0.13.0

Minor Changes

  • #211 8b93ed5 - Each devtools adapter now lists its TanStack Devtools host as an optional peer dependency at the current release, such as @tanstack/react-devtools 0.10.14. Older hosts pass the plugin a theme string instead of props, so the panel ignored the theme, and TypeScript rejects the React plugin since @tanstack/react-hotkeys-devtools 0.12.0. Package managers now warn about an old host at install time.

    Update @tanstack/devtools-utils and @tanstack/devtools-ui to 0.7.2. The Preact panel now unmounts its core on Preact 11 (fix(preact): Unmount panels on Preact 11 and pass app context to plugins devtools#551).

Patch Changes

  • Updated dependencies [8b93ed5, 8b93ed5]:
    • @tanstack/hotkeys-devtools@1.7.0

@tanstack/solid-hotkeys@0.18.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

  • #211 8b93ed5 - Providers no longer bundle app hotkey support unless the app uses defineAppHotkeys. A React app with HotkeysProvider and no app hotkeys is about 1 kB smaller (brotli).

Patch Changes

@tanstack/solid-hotkeys-devtools@0.12.0

Minor Changes

  • #211 8b93ed5 - Each devtools adapter now lists its TanStack Devtools host as an optional peer dependency at the current release, such as @tanstack/react-devtools 0.10.14. Older hosts pass the plugin a theme string instead of props, so the panel ignored the theme, and TypeScript rejects the React plugin since @tanstack/react-hotkeys-devtools 0.12.0. Package managers now warn about an old host at install time.

    Update @tanstack/devtools-utils and @tanstack/devtools-ui to 0.7.2. The Preact panel now unmounts its core on Preact 11 (fix(preact): Unmount panels on Preact 11 and pass app context to plugins devtools#551).

Patch Changes

  • Updated dependencies [8b93ed5, 8b93ed5]:
    • @tanstack/hotkeys-devtools@1.7.0

@tanstack/svelte-hotkeys@0.18.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

  • #211 8b93ed5 - Providers no longer bundle app hotkey support unless the app uses defineAppHotkeys. A React app with HotkeysProvider and no app hotkeys is about 1 kB smaller (brotli).

Patch Changes

@tanstack/svelte-hotkeys-devtools@0.4.0

Minor Changes

  • #211 8b93ed5 - Each devtools adapter now lists its TanStack Devtools host as an optional peer dependency at the current release, such as @tanstack/react-devtools 0.10.14. Older hosts pass the plugin a theme string instead of props, so the panel ignored the theme, and TypeScript rejects the React plugin since @tanstack/react-hotkeys-devtools 0.12.0. Package managers now warn about an old host at install time.

    Update @tanstack/devtools-utils and @tanstack/devtools-ui to 0.7.2. The Preact panel now unmounts its core on Preact 11 (fix(preact): Unmount panels on Preact 11 and pass app context to plugins devtools#551).

Patch Changes

  • Updated dependencies [8b93ed5, 8b93ed5]:
    • @tanstack/hotkeys-devtools@1.7.0

@tanstack/vue-hotkeys@0.18.0

Minor Changes

  • #211 8b93ed5 - Key names are case-sensitive, and key aliases are no longer resolved, which removes the key-name lookup tables from every bundle. Typed hotkeys, recording, matching, and display behave as before.

    • Spellings that the hotkey types don't allow, such as escape, Esc, f1, Plus, or pgdn, now stay as written and don't match. Use the canonical names: Escape, F1, +, PageDown. Letters still match in any case, and modifier aliases such as Ctrl, Cmd, and Option still work.
    • validateHotkey and checkHotkey warn about keys that aren't written like a known key, such as escape, instead of checking a list of key names. In development, registering such a hotkey logs a warning that it may never fire.
    • formatForDisplay accepts hotkeys only, including single keys and modifiers on their own such as 'Shift', instead of any string. Pass a key from a KeyboardEvent, such as a held key from useHeldKeys, as { key }.
    • HotkeyManager.triggerRegistration moves into the devtools package, which was its only user.
    • The recorder rejects whitespace characters, such as the non-breaking space from Option+Space on macOS, with the message "Whitespace keys cannot be recorded".
    • Saved custom hotkeys and display labels ignore names inherited from Object.prototype, such as toString. Previously, saved custom hotkeys could keep those ids, and formatForDisplay could show function source text for them.

  • #211 8b93ed5 - TanStack Hotkeys no longer depends on @tanstack/store or the framework store adapters. Its stores, such as manager.registrations and recorder.store, keep the same state, get, setState, and subscribe API and still work with TanStack Store's framework adapters. Bundles shrink by about 1.3 kB (brotli) in core and about 2.4 kB in the React adapter.

    The stores are no longer Store instances from @tanstack/store, so instanceof Store checks and other TanStack Store features, such as actions, no longer apply to them.

  • #211 8b93ed5 - Providers no longer bundle app hotkey support unless the app uses defineAppHotkeys. A React app with HotkeysProvider and no app hotkeys is about 1 kB smaller (brotli).

Patch Changes

@tanstack/vue-hotkeys-devtools@0.12.0

Minor Changes

  • #211 8b93ed5 - Each devtools adapter now lists its TanStack Devtools host as an optional peer dependency at the current release, such as @tanstack/react-devtools 0.10.14. Older hosts pass the plugin a theme string instead of props, so the panel ignored the theme, and TypeScript rejects the React plugin since @tanstack/react-hotkeys-devtools 0.12.0. Package managers now warn about an old host at install time.

    Update @tanstack/devtools-utils and @tanstack/devtools-ui to 0.7.2. The Preact panel now unmounts its core on Preact 11 (fix(preact): Unmount panels on Preact 11 and pass app context to plugins devtools#551).

Patch Changes

  • Updated dependencies [8b93ed5, 8b93ed5]:
    • @tanstack/hotkeys-devtools@1.7.0

@coderabbitai

coderabbitai Bot commented Oct 30, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@KevinVandy
KevinVandy merged commit 5d9d833 into main Oct 30, 2026
3 checks passed
@KevinVandy
KevinVandy deleted the changeset-release/main branch October 30, 2026 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@KevinVandy