-
Notifications
You must be signed in to change notification settings - Fork 88
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
Error: Undefined rule font-family-no-missing-generic-family-keyword #334
Comments
still not fixed? |
Same error with recommended config |
Same error with rule |
I'm also getting this error with Since this library appears to be unmaintained, I'd recommend this package instead: https://github.com/kennyinthirathclq/stylefmt/
Run via a
|
Gives the same error for me. Needs to be fixed. |
This bug also affects gulp-stylefmt and sublime-stylefmt. For googlers, this can be fixed easily by updating the dependencies of stylefmt:
These changes should eventually be added to stylefmt repository. |
Note to self, need to copy stylelint directly under gulp-stylefmt: |
@ronilaukkarinen I ran went into Application Support/ST3/stylefmt/node_modules/etc.... and ran npm update and then npm install for good measure. I'm still seeing the error. Did this fix it in sublime for you? |
@saltcod Nope, because stylelint is not included in the package.json of sublime-stylefmt, it comes directly from node_modules that is included within the repo, see this. Let me clarify the issue and all the others this is related. This repositoryStylelint version in package.json of stylefmt is currently 7.10.1, newest is 9.8.0. sublime-stylefmtOnly fix I've seen working is to manually overwrite globally installed stylelint folder with the newer version. Updated my devpackages Known issues for this reason and also to my WordPress theme issue tracker and also opened issue #26. gulp-stylefmtGulp-stylefmt in the other hand has old stylefmt version in package.json that needs to be update for this to get solved and stylelint version of stylefmt updated after. |
Wow. That's a lot of headache there. Looking like I can't use sublime anymore b/c we just added stylelint to our tooling, and prettier is a deal-breaker for me now. Hooray for the future. |
Yeah, for our team we have the "install global stylelint and overwrite dependencies" commands in our build scripts and workflow so that "solves" it for now, but of course I expect these to get really solved in the future. |
For reference: I still use stylefmt daily and all you need for it to work is update stylelint to latest version and run npm update... this repo has not been updated for two years now and I'm getting frustrated since at least 5 other tools (like vscode and gulp plugins referenced above) are outdated as well because of outdated stylefmt dependencies. I have emailed the maintainer if he would be willing to share access, here's one active maintainer that would close most of the issues just with I hope we get more muscle power to keep stylefmt alive as I love it. It's way better than prettier and others when developing SCSS/CSS in my honest opinion. Prettier and others concentrate too much on JS and other languages rather than CSS which is my top lang. I hope @morishitter will read these messages, there are still people who use stylefmt daily. |
FYI anyone who still might follow the stylefmt project. I have discontinued using gulp-stylefmt and sublime-stylefmt in favor of VSCode for the better part of the year. For this reason I have created vscode-stylefmt that uses my active fork of stylefmt (will release an npm package of the fork with unit tests soon!) with permission of the original maintainer of vscode-stylefmt. |
.stylelintrc
The text was updated successfully, but these errors were encountered: