Packages

css-tree

3.2.1 · 5 Mar 2026MIT183.3M / weekRepositoryHomepagenpmAtom feed

Your version

3.0.0

major11 Sep 2024Where it was published

3.2.1 is the newest release of 3.x.

In short

20 new6 fixed15 changed

Release note

  • Added support for the @container at-rule

  • Added support for the @starting-style at-rule

  • Added support for the @scope at-rule

  • Added support for the @position-try at-rule

  • Added support for the @layer at-rule

  • Added support for layer, layer() and supports() in the @media at-rule (according to the @import rule in Cascading and Inheritance 5)

  • Added Layer and LayerList node types

  • Added TokenStream#lookupTypeNonSC() method

  • Added <dashed-ident> to generic types

  • Bumped mdn/data to 2.10.0

  • Aligned <'font'> to CSS Fonts 4

  • Aligned <color> to CSS Color 5

  • Fixed initialization when Object.prototype is extended or polluted

  • Fixed fork() method to consider the generic option when creating a Lexer instance

  • Fixed crash on parse error when custom line or offset is specified via options

  • Fixed speak syntax patch

  • Fixed :lang() to accept a list of <ident> or <string> per spec

  • Fixed lexer matching for syntaxes referred to as <'property'>, when the syntax has a top-level #-multiplier

  • Relaxed parsing of syntax definition to allow whitespaces in range multiplier

  • Changed parseWithFallback() to rollback tokenIndex before calling a fallback

  • Changed Block to not include { and }

  • Changed Atrule and Rule to include { and } for a block

  • Changed Ratio parsing:

    • Left and right parts contain nodes instead of strings

    • Both left and right parts of a ratio can now be any number; validation of number range is no longer within the parser's scope.

    • Both parts can now be functions. Although not explicitly mentioned in the specification, mathematical functions can replace numbers, addressing potential use cases (#162).

    • As per the CSS Values and Units Level 4 specification, the right part of Ratio can be omitted. While this can't be a parser output (which would produce a Number node), it's feasible during Ratio node construction or transformation.

  • Changes to query-related at-rules:

    • Added new node types:

      Note: All new nodes include a kind property to define the at-rule type. Supported kinds are media, supports, and container

    • Added support for functions for features and features in a range context, e.g. (width: calc(100cm / 6))

    • Added a condition value for the parser's context option to parse queries. Use the kind option to specify the condition type, e.g., parse('...', { context: 'condition', kind: 'media' })

    • Introduced a features section in the syntax configuration for defining functional features of at-rules. Expand definitions using the fork() method. The current definition is as follows:

      features: {
          supports: { selector() { /* ... */ } },
          container: { style() { /* ... */ } }
      }
    • Changes for @media at-rule:

      • Enhanced prelude parsing for complex queries. Parentheses with errors will be parsed as GeneralEnclosed

      • Added support for features in a range context, e.g. (width > 100px) or (100px < height < 400px)

      • Transitioned from MediaFeature node type to the Feature node type with kind: "media"

      • Changed MediaQuery node structure into the following form:

        type MediaQuery = {
            type: "MediaQuery";
            modifier: string | null; // e.g. "not", "only", etc.
            mediaType: string | null; // e.g. "all", "screen", etc.
            condition: Condition | null;
        }
    • Changes for @supports at-rule:

      • Enhanced prelude parsing for complex queries. Parentheses with errors will be parsed as GeneralEnclosed

      • Added support for features in a range context, e.g. (width > 100px) or (100px < height < 400px)

      • Added SupportsDeclaration node type to encapsulate a declaration in a query, replacing Parentheses

      • Parsing now employs Condition or SupportsDeclaration nodes of kind supports instead of Parentheses

      • Added support for the selector() feature via the FeatureFunction node (configured in features.supports.selector)

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.