Packages

@asamuzakjp/dom-selector

10.0.7 · 21 Nov 2026MIT72.8M / weekRepositoryHomepagenpmAtom feed

Upgrading @asamuzakjp/dom-selector From 8.2.1 to 10.0.7

30 releases in betweennotes for 26

Reading releases, release notes and advisories…

Other targets from 8.2.1Newest 8.x8.3.2
The notes of 10.0.0, 9.0.0 list no breaking change or deprecation, which is rare for a major.
  1. 8.2.1yours
  2. 7 releases
  3. 9.0.0major
  4. 14 releases
  5. 10.0.0major
  6. 6 releases
  7. 10.0.7target
?
changes to make
0
advisories fixed
25+
new
14+
fixes

Counted from 26 of 30 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 10.0.6 – 10.0.72 releases, nothing new or fixed; 1 without a note

  2. 10.0.5

    23 Oct 20261 fix
    • Fixed

      Fix focus-visible matcher

  3. 10.0.4

    17 Oct 20261 fix
    • Fixed

      Fix preceding logic

  4. 10.0.3

    14 Oct 20261 fix
    • Fixed

      Fix extractSubjects handler

  5. 10.0.1 – 10.0.22 releases, nothing new or fixed; 1 without a note

  6. 10.0.0

    10 Oct 20261 new
    • New

      parser: Include attribute names in selector subjects

  7. 9.2.4nothing new or fixed in the note

  8. 9.2.3

    1 Oct 20261 new · 1 fix
    • New

      Add cacheSize field and update related logic

    • Fixed

      Fix nth-child parsing

38 other lines we could not sort, mostly version bumps
  • Recheck the length only when the validity value is valid

    10.0.6
  • Replace only null and unpaired surrogate characters during preprocess

    10.0.6
  • Bound the per-document selector cache

    10.0.5
  • Import constant

    10.0.5
  • Accept empty string for |= attr selector

    10.0.2
  • Move traversal methods to traverser.js

    10.0.0
  • Move private methods to other classes

    10.0.0
  • Remove regex and only use AST for subject extraction

    10.0.0
  • Freeze extracted subjects

    10.0.0
  • Use css-tree clone() instead of deep freeze

    9.2.4

4 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.