refactor: use pre-created Set for modifier key lookup in isModifierKey #188
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR replaces the inline array creation in
isModifierKeywith a pre-createdSetfor O(1) lookup, eliminating array allocation on every function call.Motivation
The
isModifierKeyfunction is called on everykeydownevent via thefocus-visiblemodule'shandleKeydownhandler. The previous implementation created a new array on every call:This means every keypress triggered:
.includes()This could contribute to typing feeling sluggish.
Changes
src/internal/keycode.ts: Create the Set once at module load time and useSet.has()for O(1) lookup:Benefits
Testing
All 17 focus-visible tests pass, including tests for each modifier key (Shift, Alt, Control, Meta).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.