Commit activity
Last 12 weeks · 69 commits
Community health
5 of 6 standards met
87
✓README✓License✓Contributing✓Code of Conduct○Issue Template✓PR Template
Recent PRs & issues
Active · Last activity 2d ago
See all on GitHub →Description When using with computed property keys in , the Vite dev server crashes with an "Invalid empty selector" error from lightningcss. This is a timing issue specific to dev mode — it does not affect production builds. Root Cause StyleX's mechanism works via a two-phase system: 1. When the babel plugin processes files, it generates "constant rules" with / metadata 2. When it processes consumer files (using computed keys like ), it generates rules with as CSS selectors 3. At CSS generation time, replaces references with actual values from the constant rules In production builds, all files are transformed before runs, so constant rules are always available and the replacement works correctly. In the Vite dev server, CSS can be requested/regenerated before all files have been processed. When this happens: doesn't find the constant values in references remain unresolved in the CSS output (e.g. ) in rejects this as invalid CSS, throwing "Invalid empty selector" The dev CSS middleware crashes The HMR mechanism () would eventually re-trigger CSS generation once all files are processed, but the error prevents the dev server from serving any CSS in the meantime. Reproduction 1. Create a file: 2. Use computed keys in a consumer file: 3. Run the Vite dev server — the terminal shows: Proposed Fix Wrap the call in () in a try-catch, falling back to the raw CSS output: This is safe because: The raw CSS with selectors is ignored by the browser (invalid selectors are skipped) Once all files are processed, the next HMR-triggered CSS update resolves all references and produces valid CSS Production builds are unaffected (all files are always processed before CSS generation) Environment : 0.17.5 : 0.17.5 Vite: 8.0.0-beta.8 Node: 22
Recent fixes
What changed / motivation ? WebkitAppearance was restricted to only 'textfield' while the standard appearance property accepts 'auto', 'none', and 'textfield'. Reuse the existing appearance rule so the vendor-prefixed variant allows the same values. Seen like a copy-paste? Linked PR/Issues n/a Additional Context n/a Pre-flight checklist [x] I have read the contributing guidelines Contribution Guidelines [x] Performed a self-review of my code
Structured data for AI agents
Repository: facebook/stylex. Description: StyleX is the styling system for ambitious user interfaces. Stars: 9129, Forks: 392. Primary language: JavaScript. Languages: JavaScript (93.2%), MDX (3.5%), TypeScript (3.2%), CSS (0.1%), Shell (0%). License: MIT. Homepage: https://stylexjs.com Latest release: 0.17.5 (1mo ago). Open PRs: 25, open issues: 95. Last activity: 2d ago. Community health: 87%. Top contributors: nmn, mellyeliu, necolas, henryqdineen, nedjulius, Prakshal-Jain, nonzzz, dwei-figma, Jta26, vincentriemer and others.