Ability to use projects version of stylelint?

[atomlinter]

Ability to use projects version of stylelint?

[egeriis]

Is it correct, that this is still not supported? We're using stylelint v6, but see errors reported that we're using rules that've been removed in stylelint v7.

[emuvente]

Implemented in #381.

[satazor]

@Arcanemagus this issue applies not only to stylint but to others too. This would indeed be a good addition, in fact I think we should always prioritize local installations. One thing to be aware though is that if we ever support this we must support API changes of stylelint runtime itself.

[satazor]

@benfrain Yes, most sublime linter providers use that philosophy which is good. We should indeed consider doing the same, but not only for stylelint but also for eslint, jshint, etc.

[EvHaus]

@Arcanemagus I can look into working on this feature. Could you give me some direction in terms of the work that needs to be done? Is it simply a manner of copying over the same way that linter-eslint does it?

[iwinux]

Temp fix:

$ ~/.atom/packages/linter-stylelint
$ vim package.json # bump stylelint version
$ yarn

[Arcanemagus]

@iwinux That has absolutely no relevance to this issue here. 😕

[Arcanemagus]

This is of course possible, it just complicates how things are ran quite a bit. A PR implementing this would be nice!

[benfrain]

The Sublime version of stylelint already works this way: https://github.com/kungfusheep/SublimeLinter-contrib-stylelint

That's why I was surprised the Atom one didn't.

On 1 Jan 2016, at 18:41, André Cruz [email protected] wrote:

@Arcanemagus this issue applies not only to stylint but to others too. This would indeed be a good addition, in fact I think we should always prioritize local installations. One thing to be aware though is that if we ever support this we must support API changes of stylelint runtime itself.

—
Reply to this email directly or view it on GitHub.

[Arcanemagus]

@satazor linter-eslint already works in this manner, ideally all node based linters should work in this manner.

[silvenon]

I was wondering why the CLI and linter-stylelint were reporting differently 👍

[jaydenseric]

This is critical, I can't use this plugin with the current version of stylelint (5.0.0). A notification pops up with the error "Unable to run stylelint" due to undefined rules. Running stylelint via a NPM script is fine.

[Arcanemagus]

@jaydenseric A PR for this would be welcome, in the meantime v5.0.0 is actually ready, just waiting on the configs to update (#122).

[Arcanemagus]

@jaydenseric v2.0.0 is published which bundles [email protected], do note that the only config that currently works with this version of stylelint is stylelint-config-standard (at least of the 4 that were previously bundled).

[ntwb]

I made a comment in #134 where I stated:

"This is the downside of the Atom linters installing the linters themselves vs the Sublime Text way is that you should install the linter somewhere or globally yourself before adding the editor package."

My, bad, apologies, I also didn't know linter-eslint already worked in this manner, so it would be great to see linter-stylelint also work this same way 👍

[jonrohan]

Bump on this 👍

[ai]

I need this feature too :)

[boxxxie]

i can't use stylelint in it's current form

i get the below error. i think it's related to this issue.

Unable to run stylelint
Undefined rule "declaration-block-no-redundant-longhand-properties"

[ai]

Me too have Undefined rule "declaration-block-no-redundant-longhand-properties" error right after update to Stylelint 7.2.

[Arcanemagus]

That's because this package hasn't been updated to bundle [email protected] yet, hence why this issue exists in the first place 😛.

I'll push out an update with that in a few.

Edit: Published in v3.2.0.

[MattDiMu]

@iwinux How is this a fix and how does this give you the possibility to use different stylelint-versions for different projects? (= not being forced to update older projects all the time)

[Arcanemagus]

@EvHaus This is a rather large undertaking, the best example of doing this correctly that we have currently is this function and the functions it calls / settings it uses over in linter-eslint.

[dkniffin]

Has any progress been made on this? It's been almost two years since it was suggested, and it's such an important feature for anyone who works on projects that aren't using the latest version of stylelint. Without it, this plugin is essentially useless for those projects.