Closed efueger closed 4 years ago
Also note that I'm using "extends" with a package from npm (containing stylelint rule set).
I also noted the following on another repo I maintain:
Both of those branch HEADs are after I changed to the package.json layout + stylelint rule package.
@efueger @andersevenrud
I think the problem isn't about the config being in the package.json but with CodeClimate since they don't install packages in their infra.
If you try to load a package that this engine doesn't support, like @osjs/stylelint-config
it will break,
@gilbarbara Does this apply to the standard stylelint extensions as well ?
Edit: Sorry, I totally read that wrong. I now see the list of supported ones.
I'll have to look into alternatives.
@efueger You can close this issue. As mentioned in my previous [edited] comment, I'll find an alternate way of running a stylelint check.
@gilbarbara - Emily here from Code Climate Support 👋
A customer wrote in reporting they recently migrated over from using stylelint's .stylelintrc file to a "stylelint" property in package.json and now it seems that stylelint is broken.
Let me know if I can provide any additional details. Thanks!