no-unnecessary-polyfills: Improve performance#2874
Merged
Conversation
Repository owner
deleted a comment
Feb 11, 2026
fisker
reviewed
Feb 13, 2026
Collaborator
fisker
left a comment
fisker
left a comment
There was a problem hiding this comment.
Didn't read the code, feel free to merge.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The rule was doing too many regex checks per import. I changed it to preselect likely matches before running regex tests. It now builds token indexes from core-js feature names and only checks candidate patterns. I also normalized polyfill-prefixed imports (polyfill-* and mdn-polyfills/*) so they use the same narrowed path instead of scanning everything.
Result: overhead on synthetic 4000-import files dropped from roughly 2x+ in some cases to about 1.0-1.06x.