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
There appear to be some valid cases where the input to the parser is not a string. For instance, svg-load function from postcss-inline-svg results in a value.charCodeAt is not a function error.
I could try! I'm actually not 100% sure what the expected behavior is in this case. I encountered this trying to use postcss-inline-svg in webpack, (which I believe you also maintain), with svgo and postcss-assets and kept getting this same error, both of which have a dependency on postcss-value-parser. I'm having a hard time wrapping my head around how everything interrelates, since I'm rather new to using postcss.
Activity
TrySound commentedon Jun 27, 2016
@amaschas Would you like to send a PR? :)
amaschas commentedon Jun 27, 2016
I could try! I'm actually not 100% sure what the expected behavior is in this case. I encountered this trying to use postcss-inline-svg in webpack, (which I believe you also maintain), with svgo and postcss-assets and kept getting this same error, both of which have a dependency on postcss-value-parser. I'm having a hard time wrapping my head around how everything interrelates, since I'm rather new to using postcss.
TrySound commentedon Jun 27, 2016
@amaschas There was an issue with postcss-inline-svg@2 some time ago. Did you tried fixed 2.0.1?
TrySound commentedon Jun 27, 2016
PR may contain just if statement with more convinient error. With test case of cause:)
amaschas commentedon Jun 27, 2016
Sure, I'll find some time to do that this week.
Updating to 2.0.1 did in fact fix my issue. Thank you!
TrySound commentedon Jun 27, 2016
Glad to hear :)