New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS Linter failing after upgrade to postcss version 8.4 and above. #1685
Comments
We still have this method https://github.com/postcss/postcss/blob/main/lib/node.js#L260 You need to ask your linter developers. |
Thanks for the inputs, looks like upgrading stylelint to latest version will fix the issue for us. So closing the issue. |
If this can help anyone else. |
We are facing the issue on 8.4.4 itself @emilie-t-ledn . |
@ai Are there any updates regarding this issue? |
It is related to different PostCSS versions in We had a protection against broken AST, but I have no idea why it is not calling here https://github.com/postcss/postcss/blob/main/lib/container.js#L320 |
@ai Is there any update on this issue? |
I didn’t find a why it happens and how to fix it. If you help me, it will be very nice. |
After the recent releases of postcss versions 8.4 and above our css linters have started to fail due to the following error message:
TypeError: opts.node.rangeBy is not a function
. Attaching screenshot of the full error logWe have downgraded postcss to
8.3.11
. Any guidance towards fixing the issue is appreciated. Thanks in advance.@ai
The text was updated successfully, but these errors were encountered: