Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

'Selector' option throws TypeError

See original GitHub issue

With the ‘selector’ option set to true using 6.0.0, the plugin throws the following error. This occurs even without any selectors being built with calc() in my stylesheets.

TypeError: Cannot read property 'charCodeAt' of undefined
  at module.exports (fakepath/node_modules/postcss-value-parser/lib/parse.js:17:21)
  at new ValueParser (fakepath/node_modules/postcss-value-parser/lib/index.js:7:22)
  at ValueParser (fakepath/node_modules/postcss-value-parser/lib/index.js:10:12)
  at exports.default (fakepath/node_modules/postcss-calc/node_modules/reduce-css-calc/dist/index.js:29:43)
  at transformValue (fakepath/node_modules/postcss-calc/dist/lib/transform.js:20:45)
  at fakepath/node_modules/postcss-calc/dist/lib/transform.js:36:19
  at fakepath/node_modules/postcss-selector-parser/dist/selectors/container.js:170:26
  at Selector.each (fakepath/node_modules/postcss-selector-parser/dist/selectors/container.js:153:22)
  at Selector.walk (fakepath/node_modules/postcss-selector-parser/dist/selectors/container.js:169:21)
  at fakepath/node_modules/postcss-selector-parser/dist/selectors/container.js:173:31

Running through the gulp-postcss 7.0.0, which is using PostCSS 6.0.0

Issue Analytics

State:
Created 6 years ago
Reactions:4
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

wenkanglincommented, Jul 10, 2017

Thank you for answer. The first option is correct fix the issue for me. But we often inevitably encounter code like below:

button[disabled] {}

@mjschlot you should submit a pr and wait merged by author. 👍

1reaction

mjschlotcommented, Jul 9, 2017

The issue appears to be related to selectors like: abbr[title] This situation exists in packages like normalize.css (https://github.com/necolas/normalize.css/blob/master/normalize.css).

Possible fix would be to test if node.value is undefined in transform.js if (node.type === 'attribute' && node.value !== undefined) {

I’m not familiar enough with postcss to know if this is the best fix though.