-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
Stylelint not working out-of-the-box #1028
Comments
I've found the same error after creating a new Nuxt project. Very ugly. |
@josepcrespo did my solution work for you? |
opened PR at #1029 |
@MatanelGordon works for me, thx. I don't know why this problem still occurs today, it's really annoying |
I got the same issue today after a fresh installation using
This was the generated package.json content mentioned in the previous comment:
I removed the
So I can confirm that the issue is still present and that the solution proposed by @MatanelGordon works. Thank you! |
I have updated |
Just to be clear, my solution refers to I encourage you to open an issue at |
Thanks for your response, MatanelGordon. I'd like to clarify that I'm actually using Nuxt V2, and I encountered the same issue. It seems there might be some confusion regarding the @nuxtjs/stylelint-module package. While you mentioned it's for Nuxt V3, I believe it's also present in Nuxt V2. I'll still consider opening an issue on Github to address this, but I thought it's important to clarify the version I'm working with. |
TS config was removed |
Changed to array |
Thanks @MatanelGordon |
Version
create-nuxt-app: v5.0.0
Steps to reproduce
What is Expected?
When running
yarn lint:style
should not throw warning when nothing changed.What is actually happening?
When running
yarn lint:style
I get the following error:This means it doesn't recognize the used class names in vue's template.
How I solved it?
I updated the dependencies of the following packages:
Also, I removed
stylelint-config-prettier
.the final stylelint should look like the follows:
found the solution in a problem in stylelint's issues in addition to the migration guide for stylelint v15 which stated:
The text was updated successfully, but these errors were encountered: