perf: optimize CSS selector pruning#17846
Merged
Rich-Harris merged 3 commits intoMar 3, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 96ebbc7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Merged
Rich-Harris
pushed a commit
that referenced
this pull request
Mar 3, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 ## svelte@5.53.7 ### Patch Changes - fix: correctly add \_\_svelte_meta after else-if chains ([#17830](#17830)) - perf: cache element interactivity and source line splitting in compiler ([#17839](#17839)) - chore: avoid rescheduling effects during branch commit ([#17837](#17837)) - perf: optimize CSS selector pruning ([#17846](#17846)) - fix: preserve original boundary errors when keyed each rows are removed during async updates ([#17843](#17843)) - perf: avoid O(n²) name scanning in scope `generate` and `unique` ([#17844](#17844)) - fix: preserve each items that are needed by pending batches ([#17819](#17819)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
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.
Summary
Reduces CSS selector pruning overhead by eliminating unnecessary allocations and redundant work in the hot path.
Changes:
.slice()+.shift()/.pop()inapply_selectorwith index-basedfrom/toparams — avoids O(n) array copies per recursive callhas_selectors/other_selectorssplit inrelative_selector_might_apply_to_nodeinto a single pass — eliminates 2 temporary array allocations per callname.toLowerCase()out of the inner loop inattribute_matchesvalue.split(/\s/).includes()withindexOf+ boundary checks intest_attributefor~=— avoids array allocation on every class matchname.replace()regex when selector name has no backslashBenchmark
Interleaved benchmark (5 rounds, alternating baseline/optimized):
CPU profile before → after:
relative_selector_might_apply_to_nodeattribute_matchestest_attributeTest plan
css-prune-edge-casestest covering:~=word matching (substring vs whole word), deep combinator chains (4+ levels),:has()combined with class selectors, escaped selectors,:is()/:where()/:not()with combinators🤖 Generated with Claude Code