Masafumi Koba

@kristerkari Your concern makes sense. I can't get a nice idea for now. 😓 Probably, we should have supported the `resolveNestedSelectors` option for all the rules depending on `postcss-resolve-nested-selector`'s identifier...

> Would it be possible to add, to these rules, a secondary option that accepts a function to transform the selectors? Adding an `ignore*` secondary option sounds great! If this...

When I looked for candidates, I found 2 packages: - [`stylelint-formatter-github`](https://www.npmjs.com/package/stylelint-formatter-github) - Most popular, presented in Awesome Stylelint, but inactive - [`stylelint-actions-formatters`](https://www.npmjs.com/package/stylelint-actions-formatters) - Active, considering the newer API (problem matcher)...

I just added `stylelint-actions-formatters` in https://github.com/stylelint/awesome-stylelint/pull/70

> So I'll contact an author of `stylelint-actions-formatters`. Done: https://github.com/xt0rted/stylelint-actions-formatters/issues/187

Since I found an alternative package, I've labeled the issue as **ready to implement**. Please consider [contributing](https://stylelint.io/contributing) if you have time. `process.emitWarning()` like #7550 will output a deprecation warning if...

@henryruhs Can you provide more details on the problem in your plugin? What do you expect?

@henryruhs Just to be sure, `@isnotdefined/[email protected]` has resolved this problem, right?

Can you provide a reproducible demo/code with `@isnotdefined/[email protected]`?

Thanks. I can now reproduce the deprecation warning with the patched `@isnotdefined/[email protected]` 👍🏼 ```diff --- node_modules/@isnotdefined/stylelint-plugin/package.json.orig 2024-02-21 13:20:26 +++ node_modules/@isnotdefined/stylelint-plugin/package.json 2024-02-21 13:19:57 @@ -62,7 +62,7 @@ }, "exports": { -...