Seleree is a fast selector decision tree for matching CSS selectors to elements and selecting the best matching handler. It builds a tree from selector and value pairs, then uses plugins to generate runnable pickers for specific DOM implementations (for example, HTML parser output), useful for efficiently applying handlers during DOM processing.
Project status
- The GitHub upstream shows an activity signal, with the last upstream push on 2026-05-02, but the most recent version update listed is v0.11.0 dated 2023-02-23, so published npm updates appear infrequent in recent years.
- Apparent update cadence is bursty and not frequent by today’s date, with gaps of roughly 1 to 3 years between the documented updates (2021-11, 2022-02, 2022-12, 2023-02), despite that newer commits exist in 2026.
AI summary generated
Recent updates
v0.11.0
v0.11.0 updates the selderee selector-decision-tree library and the @selderee/plugin-htmlparser2 wrapper. No publisher release notes were provided, and the actual diff shows changes centered on upgrading the selector parser dependency (parseley) and adding test coverage for escape sequences and non-ASCII selector inputs.
0.10.0
Version 0.10.0 significantly upgrades the project toolchain and runtime targeting to Node.js 14 and ES2020. It also bumps several dependencies (including a major domhandler upgrade) and changes the Rollup build output format and file naming for published artifacts.
Breakingv0.9.0
Version v0.9.0 was released on 2022-02-03, but the publisher provided no release notes. As a result, there is no documented information about new features, bug fixes, breaking changes, or security updates in this release.
v0.8.1
v0.8.1 contains mainly dependency and build pipeline changes. There are no release notes provided for the version itself, but the diff shows updates to core packaging (sideEffects) and a dependency bump for parseley, plus changes to rollup publishing behavior via rollup-plugin-cleanup.
Breakingv0.7.0
Release v0.7.0 was published on 2021-11-10, but no release notes were provided by the publisher. As a result, the release cannot be validated for specific new features, bug fixes, security fixes, or breaking changes based on the provided information.