Masafumi Koba

@romainmenke Thanks for creating the package so quickly. It's fantastic! Yes, your understanding is correct, and my question was bad. As you commented, keeping an original source position is almost...

I'd like to use `@csstools/selector-resolve-nested` soon instead of `postcss-resolve-nested-selector`, but we may not be able to do that since there are compatibility issues in `postcss-resolve-nested-selector` (see #7482).

@romainmenke Thanks a lot for the further investigation. My understanding of [`selector-max-type`](https://github.com/stylelint/stylelint/tree/382961fb6eb67557910a1ff7430a7a180f888bcc/lib/rules/selector-max-type) is like this: ```json { "rules": { "selector-max-type": 2 } } ``` ```css foo #y, .z bar {...

@d-fischer Great, thank you so much!

PR #6491 updates `cosmiconfig` to 8.0.0. Note that the PR's base branch is `v15`. That means Stylelint 15.0.0 will include the new major version of `cosmiconfig`.

Closed via #6491

Um, I don't remember, sorry. 😓 But, if someone published a plugin for this feature, we could evaluate whether we should bring it to the Stylelint core.

@Mouvedia Sorry that my comment confused you. As @jeddy3 suggested, let's stop this now. We've recently started considering a new configuration system and CLI defaults (#7408 and #7409). The situation...

@Mouvedia Sorry for the sudden reversal. But you still have not answered my question (https://github.com/stylelint/stylelint/pull/7252#issuecomment-1849021378) since I was surprised by the `--merge-rules` suddenly came. You should have confirmed that the...

@Mouvedia I believe there is still room to discuss new CLI flags and syntax for configuring a rule before entering implementation details. Also, if a 3rd-party package would do the...