csstree

🚀 VSCode CSSTree validator v1.2 Now powered by CSSTree 3.0, featuring enhanced warnings for unknown properties, descriptors, and at-rules. Improved error highlighting makes catching CSS issues easier than ever. marketplace.visualstudio.com/items?itemName…

🚀 CSSTree validator v4.0 Now powered by the latest CSSTree 3.0, featuring enhanced support for modern CSS syntax. Check it out! github.com/csstree/valida…

🚀 CSSTree 3.0 is here! Featuring support for modern at-rules, improvements to query-related at-rules, spec alignments, other enhancements and bug fixes, and more. Release notes: github.com/csstree/csstre…

💖 These two months, we redistributed our funds to @satanacchio, @johnsoncodehk, @geteslint, libvips, @csstree, Discovery.js, @pnpmjs, @iconify_design for their amazing work! 🙏 Thanks to @logto_io and all the sponsors for making this possible! opencollective.com/antfu/updates/…

I've just contributed to @csstree. Consider supporting them too — every little helps! opencollective.com/csstree via @opencollect

@projectwallace Could you clarify, please, what’s going wrong? Maybe it will be more convenient to discuss on GitHub?

@projectwallace Most part of it is a syntax definition dictionary. It can be tree-shaken in theory, but it’s complicated in general. You may try to import lexer alone and use your own dictionary for it (see exports section in readme #exports" target="_blank" rel="nofollow noopener">github.com/csstree/csstre…)

@projectwallace See “Syntax matching” in usage section of readme #usage" target="_blank" rel="nofollow noopener">github.com/csstree/csstre… It also should work with string values beside of AST nodes.

🚀 CSSTree 2.3.0 CSS Nesting support, units introspection and customisation, up to date mdn/data dictionary github.com/csstree/csstre…

[New blog post] How we improved the CSS formal syntax sections on @MozDevNet with the help of @csstree (h/t @rdvornov) and the @w3cdevs webref/css package openwebdocs.org/content/posts/…

@jon_neal @bartveneman @bramus @ChromiumDev @Una @jh3yy @PostCSS @projectwallace Could you clarify please, what is “the convenient API to manipulate values”?

@bartveneman @bramus @ChromiumDev @Una @jh3yy @csstree @PostCSS @projectwallace Let’s say I want to write a polyfill for container queries, the recent nesting survey proposals, or custom units. I would need to parse (CSS3) syntactic "component values". CSSTree may not provide the convenient API to manipulate these values, & PostCSS would not parse values.

📅❗️Happening tomorrow: Join us for our Modern UI AMA. @Una, @bramus, and @jh3yy are going live to answer your burning questions. 🔥 Ask your question below for a chance to have it answered in the Space! twitter.com/i/spaces/1gqxv…

Looks like CSSTree's definition syntax matching with an appropriate dictionary could be used for SVG attribute validation:

⭐️ Updated CSS syntax reference to use latest CSSTree and mdn/data dictionaries csstree.github.io/docs/syntax/

🚀 CSSTree validator 3.0 Use latest CSSTree, ESM support, custom reporters for CLI Release notes: github.com/csstree/valida…

🚀 stylelint-validator 2.0 Implemented at-rule validation, improved ignore options and Sass/Less syntax extensions, ESM support Release notes: github.com/csstree/stylel…

🚀 CSSTree 2.0.2 Polishing and bug fixes, reduce install size Release notes and details: github.com/csstree/csstre…

@justinfagnani Just in case, CSSTree 2.0 is migrated to ESM (CommonJS is also supported) github.com/csstree/csstre…

Anyone know of any CSS parser published to npm as standard JS modules? PostCSS and CSSTree aren't.

📦 Package of the Day css-tree npmjs.com/package/css-tr… CSSTree is a toolset for CSS; fast detailed parser, walker, generator and lexer (validation and matching) based on specs and browser implementations. #javascript #nodejs #npmPackageOfTheDay #100DaysOfCode

@rtsao @devongovett CSSTree is such tool github.com/csstree/csstree It uses CSS definition syntax to match values You can try to test a value against a syntax using this playground #Property:background" target="_blank" rel="nofollow noopener">csstree.github.io/docs/syntax/#P…

@devongovett Yeah, I’m not aware of any parsers (that aren’t part of a browser) that handle complex background shorthands correctly. I gave up and used the style crate from Servo/FF github.com/rtsao/cssparse

Writing a CSS parser is harder than it looks. Each property essentially has it's own mini grammar. And there are over 500 different properties... 🤯 Some are very flexible too, e.g. many shorthands accept their arguments in any order and allow any of them to be omitted.

CSSTree v2’s tokenizer is the absolute fastest, with a comfortable lead, and the semantically correct number of tokens. @rdvornov even fixed tests that inaccurately benchmarked CSSTree v1. Thank you, from the web. github.com/csstools/token…