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
In postcss-values-parser v2, String(node) returns the string value of any Node. In postcss-values-parser v3, one must now use the nodeToString function to retrieve the string value. Worse yet, when a node is accidentally toString’d, an error is thrown!
I would prefers things work the same as they did in v2, as well as how they still do in PostCSS.
Expected Behavior / Situation
In postcss-values-parser v2,
String(node)
returns the string value of anyNode
. In postcss-values-parser v3, one must now use thenodeToString
function to retrieve the string value. Worse yet, when a node is accidentallytoString
’d, an error is thrown!I would prefers things work the same as they did in v2, as well as how they still do in PostCSS.
And here is an example of the stringified behavior currently in PostCSS:
Actual Behavior / Situation
Modification Proposal
Remove the
TypeError: this[node.type] is not a function
error and defaulttoString
to work likenodeToString
.The text was updated successfully, but these errors were encountered: