Skip to content
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

Enable compatibility with stylelint 16.x #299

Closed
swcm-mnestler opened this issue Dec 11, 2023 · 2 comments · Fixed by #301
Closed

Enable compatibility with stylelint 16.x #299

swcm-mnestler opened this issue Dec 11, 2023 · 2 comments · Fixed by #301

Comments

@swcm-mnestler
Copy link

Like back in #273, stylelint 16 is released and this project's peer dependency constraints doesn't allow it. Several deprecated rules were removed in the new version, so it might take a bit of effort to upgrade.

npm ERR! While resolving: stylelint-config-sass-guidelines@10.0.0
npm ERR! Found: stylelint@16.0.1
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"^16.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@"^15.2.0" from stylelint-config-sass-guidelines@10.0.0
npm ERR! node_modules/stylelint-config-sass-guidelines
npm ERR!   dev stylelint-config-sass-guidelines@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: stylelint@15.11.0
npm ERR! node_modules/stylelint
npm ERR!   peer stylelint@"^15.2.0" from stylelint-config-sass-guidelines@10.0.0
npm ERR!   node_modules/stylelint-config-sass-guidelines
npm ERR!     dev stylelint-config-sass-guidelines@"10.0.0" from the root project
@echoix
Copy link

echoix commented Dec 12, 2023

The tool will need to be disabled in Megalinter to not hold back the other stylelint tools, like with the previous major release.

@bjankord
Copy link
Owner

stylelint v16.x support has been released in v11.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants