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
{{ message }}
This repository has been archived by the owner on Dec 28, 2021. It is now read-only.
Processing my css files with the newly released PostCSS 8, I get the error below:
TypeError: string is not iterable
at Object.split (<omitted>\node_modules\postcss\lib\list.js:13:24)
at Object.comma (<omitted>\node_modules\postcss\lib\list.js:51:17)
at Rule.get selectors [as selectors] (<omitted>\node_modules\postcss\lib\rule.js:14:17)
at isRuleWithinRule (<omitted>\node_modules\postcss-nesting\index.cjs.js:51:102)
at <omitted>\node_modules\postcss-nesting\index.cjs.js:114:11
at Array.forEach (<anonymous>)
at walk (<omitted>\node_modules\postcss-nesting\index.cjs.js:112:23)
at <omitted>\node_modules\postcss-nesting\index.cjs.js:125:9
at Array.forEach (<anonymous>)
at walk (<omitted>\node_modules\postcss-nesting\index.cjs.js:112:23)
at LazyResult.runOnRoot (<omitted>\node_modules\postcss\lib\lazy-result.js:287:16)
at LazyResult.runAsync (<omitted>\node_modules\postcss\lib\lazy-result.js:339:26)
at async Promise.all (index 21)
I don't know if the new version is triggering a bug in postcss-nesting or if it simply needs to be made compatible. Let me know if you need an actual testcase (I'm just filing this quickly to make you aware).
The text was updated successfully, but these errors were encountered:
I no longer see this issue with PostCSS 8.0.9, so it looks like this was a bug in PostCSS itself. Of course the desire for migration still applies, but I'll close this as the first comment would be misleading.
Processing my css files with the newly released PostCSS 8, I get the error below:
I don't know if the new version is triggering a bug in postcss-nesting or if it simply needs to be made compatible. Let me know if you need an actual testcase (I'm just filing this quickly to make you aware).
The text was updated successfully, but these errors were encountered: