User tests: Successful: Unsuccessful:
Pull Request resolves build error in PR #47994
The vendor CSS versioning step (build/build-modules-js/stylesheets/css-versioning.mjs) runs every CSS file in media/vendor through lightningcss, which fully parses and re-serialises the file in order to append cache-busting versions to url(...) references.
The problem: lightningcss does not just rewrite URLs, it semantically parses the whole stylesheet. As soon as a vendor package ships modern CSS syntax that the bundled lightningcss version cannot parse yet, the parser throws and the entire build aborts.
See PR #47994 from @brianteeman https://github.com/joomla/joomla-cms/actions/runs/27872556107/job/82563289058?pr=47994
This PR adds a non-destructive fallback:
This is more robust long-term for vendor CSS (TinyMCE, Bootstrap, FontAwesome, …), since those packages can introduce new valid CSS syntax at any time.
The build aborts with an error such as:
Error: SyntaxError: Unexpected token Ident("of")
at fixVersion (.../build-modules-js/stylesheets/css-versioning.mjs)
No CSS is versioned and the build fails.
The build completes. The unparseable file logs a fallback notice (Could not parse … Falling back to text-based url() versioning.), its url(...) references receive a version query, and all other CSS — including the syntax lightningcss could not parse — is preserved byte-for-byte.
Please select:
| Status | New | ⇒ | Pending |
| Category | ⇒ | JavaScript Repository |
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-06-22 09:48:17 |
| Closed_By | ⇒ | HLeithner | |
| Labels |
Added:
PR-6.1-dev
|
||
I have tested this item ✅ successfully on 54e4a02
Tested with PR #47994 (TinyMCE update):
Thanks very much
I have tested this item ✅ successfully on 54e4a02
Tested with PR #47994 (TinyMCE update):
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47996.