Wrangler hotkeys are case sensitive

[NuroDev]

Currently if you try and use and of Wrangler's build in hotkeys when running the dev server, such as pressing x to close the dev server, or b to open the browser, the key detection is case sensitive.

This means even if you have caps lock enabled and try to use these features it won't work.

[penalosa]

/bonk open a PR to fix this issue

[ask-bonk]

Here's a summary of the fix:

Problem

Wrangler's dev server hotkeys (b to open browser, x/q to exit, etc.) were case-sensitive. When Caps Lock was enabled or Shift was held, Node.js readline emits key events with key.shift = true and key.name as the lowercase letter. The hotkey matcher in cli-hotkeys.ts would construct "shift+b" from this, which didn't match the registered key "b" — silently ignoring the keypress.

Fix

In packages/wrangler/src/cli-hotkeys.ts:93-94, when only shift is the active modifier (no ctrl or meta), the matcher now also tries the plain key name without the "shift+" prefix. This means:

• b with Caps Lock on → key.shift=true, constructs "shift+b", but also tries "b" → matches
• Ctrl+C → still only matches "ctrl+c" (shift fallback only applies when shift is the sole modifier)
• Explicit shift+a bindings still work via exact match

Tests added

3 new test cases in packages/wrangler/src/__tests__/cli-hotkeys.test.ts:

1. "handles CAPSLOCK" — extended to test realistic terminal behavior (key.name="a", key.shift=true)
2. "prefers explicit shift binding over fallback" — verifies both exact shift+a and plain a handlers fire
3. "does not strip ctrl or meta modifiers" — ensures ctrl+a and meta+a don't accidentally match plain a

github run