You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When processing at-rules, postcss-functions expect the node to have a "params" entry but not all at-rules have params. So node.params can be undefined and cause an error when passed to postcss-value-parser.
The transformString() function should check if a proper string is supplied and fallback to an empty string or avoid parsing if not.
I never had any troubles with PostCSS and font-face rules before. I only notice this bug after a recent update. Apparently my occurrence of the bug is triggered by postcss-font-magician which inject its own at-rules with no params entry (which is not a bug).
The text was updated successfully, but these errors were encountered:
rubycon
changed the title
Lack robustness with some at-rules
Lax argument validation cause crash with some at-rules
Jun 30, 2021
When processing at-rules,
postcss-functions
expect the node to have a "params" entry but not all at-rules have params. Sonode.params
can be undefined and cause an error when passed topostcss-value-parser
.postcss-functions/src/lib/transformer.mjs
Lines 65 to 69 in d834e0a
The
transformString()
function should check if a proper string is supplied and fallback to an empty string or avoid parsing if not.I never had any troubles with PostCSS and font-face rules before. I only notice this bug after a recent update. Apparently my occurrence of the bug is triggered by
postcss-font-magician
which inject its own at-rules with noparams
entry (which is not a bug).The text was updated successfully, but these errors were encountered: