Stylelint v16 deprecated CJS so I moved our lint script to ESM, and fixed all the deprecation warning. The only place I needed to silence them were tests, as we import CJS there. Bug: none Change-Id: Iae4d2df76c855a9738b774a2d035f22509770215 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6138610 Commit-Queue: Nikolay Vitkov <nvitkov@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
CSS Parser Algorithms
Implemented from : https://www.w3.org/TR/2021/CRD-css-syntax-3-20211224/
API
Usage
Add CSS Parser Algorithms to your project:
npm install @csstools/css-parser-algorithms @csstools/css-tokenizer --save-dev
CSS Parser Algorithms only accepts tokenized CSS.
It must be used together with @csstools/css-tokenizer.
import { tokenizer, TokenType } from '@csstools/css-tokenizer';
import { parseComponentValue } from '@csstools/css-parser-algorithms';
const myCSS = `@media only screen and (min-width: 768rem) {
.foo {
content: 'Some content!' !important;
}
}
`;
const t = tokenizer({
css: myCSS,
});
const tokens = [];
{
while (!t.endOfFile()) {
tokens.push(t.nextToken());
}
tokens.push(t.nextToken()); // EOF-token
}
const options = {
onParseError: ((err) => {
throw err;
}),
};
const result = parseComponentValue(tokens, options);
console.log(result);
Available functions
Utilities
gatherNodeAncestry
The AST does not expose the entire ancestry of each node. The walker methods do provide access to the current parent, but also not the entire ancestry.
To gather the entire ancestry for a a given sub tree of the AST you can use gatherNodeAncestry.
The result is a Map with the child nodes as keys and the parents as values.
This allows you to lookup any ancestor of any node.
import { parseComponentValue } from '@csstools/css-parser-algorithms';
const result = parseComponentValue(tokens, options);
const ancestry = gatherNodeAncestry(result);
Options
{
onParseError?: (error: ParseError) => void
}
onParseError
The parser algorithms are forgiving and won't stop when a parse error is encountered. Parse errors also aren't tokens.
To receive parsing error information you can set a callback.
Parser errors will try to inform you about the point in the parsing logic the error happened. This tells you the kind of error.
Goals and non-goals
Things this package aims to be:
- specification compliant CSS parser
- a reliable low level package to be used in CSS sub-grammars
What it is not:
- opinionated
- fast
- small
- a replacement for PostCSS (PostCSS is fast and also an ecosystem)