css-tree
3.2.1 · 5 Mar 2026MIT183.3M / weekRepositoryHomepagenpmAtom feed
3.2.1 is the newest release of 3.x.
In short
20 new6 fixed15 changed
Release note
Added support for the
@containerat-ruleAdded support for the
@starting-styleat-ruleAdded support for the
@scopeat-ruleAdded support for the
@position-tryat-ruleAdded support for the
@layerat-ruleAdded support for
layer,layer()andsupports()in the@mediaat-rule (according to the @import rule in Cascading and Inheritance 5)Added
LayerandLayerListnode typesAdded
TokenStream#lookupTypeNonSC()methodAdded
<dashed-ident>to generic typesBumped
mdn/datato2.10.0Aligned
<'font'>to CSS Fonts 4Aligned
<color>to CSS Color 5Fixed initialization when
Object.prototypeis extended or pollutedFixed
fork()method to consider thegenericoption when creating a Lexer instanceFixed crash on parse error when custom
lineoroffsetis specified via optionsFixed
speaksyntax patchFixed
:lang()to accept a list of<ident>or<string>per specFixed lexer matching for syntaxes referred to as
<'property'>, when the syntax has a top-level#-multiplierRelaxed parsing of syntax definition to allow whitespaces in range multiplier
Changed
parseWithFallback()to rollbacktokenIndexbefore calling a fallbackChanged
Blockto not include{and}Changed
AtruleandRuleto include{and}for a blockChanged
Ratioparsing: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
Ratiocan be omitted. While this can't be a parser output (which would produce aNumbernode), it's feasible duringRationode construction or transformation.
Changes to query-related at-rules:
Added new node types:
Feature: represents features like(feature)and(feature: value), fundamental for both@mediaand@containerat-rulesFeatureRange: represents features in a range contextFeatureFunction: represents functional features such as@supports'sselector()or@container'sstyle()Condition: used across all query-like at-rules, encapsulating queries with features and thenot,and, andoroperatorsGeneralEnclosure: represents the<general-enclosed>production, which caters to unparsed parentheses or functional expressions
Note: All new nodes include a
kindproperty to define the at-rule type. Supported kinds aremedia,supports, andcontainerAdded support for functions for features and features in a range context, e.g.
(width: calc(100cm / 6))Added a
conditionvalue for the parser's context option to parse queries. Use thekindoption to specify the condition type, e.g.,parse('...', { context: 'condition', kind: 'media' })Introduced a
featuressection in the syntax configuration for defining functional features of at-rules. Expand definitions using thefork()method. The current definition is as follows:features: { supports: { selector() { /* ... */ } }, container: { style() { /* ... */ } } }Changes for
@mediaat-rule:Enhanced prelude parsing for complex queries. Parentheses with errors will be parsed as
GeneralEnclosedAdded support for features in a range context, e.g.
(width > 100px)or(100px < height < 400px)Transitioned from
MediaFeaturenode type to theFeaturenode type withkind: "media"Changed
MediaQuerynode 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
@supportsat-rule:Enhanced prelude parsing for complex queries. Parentheses with errors will be parsed as
GeneralEnclosedAdded support for features in a range context, e.g.
(width > 100px)or(100px < height < 400px)Added
SupportsDeclarationnode type to encapsulate a declaration in a query, replacingParenthesesParsing now employs
ConditionorSupportsDeclarationnodes of kindsupportsinstead ofParenthesesAdded support for the
selector()feature via theFeatureFunctionnode (configured infeatures.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.