Richard Hallows

Closing in favour of https://github.com/stylelint/css-parser/issues/2

@skepsys Thank you for digging into it some more. We [assume that](https://github.com/stylelint/stylelint/blob/main/lib/rules/no-duplicate-selectors/index.js#L76) syntaxes will provide a `source`, but it seems `postcss-sass` does not. I'll label as discussion as we can...

Labelling as ready to implement following the discussion in https://github.com/stylelint/stylelint/issues/6689. Picking up https://github.com/stylelint/stylelint/issues/6689#issuecomment-1469041369 Let's support strings and an array of strings to be consistent with the other options, including all...

There's quite a bit to consider here. We want to enable `{"lint": "xo && stylelint"}` while also being compatible with a future flat config. I believe this is possible. With...

> Can you separate this into its own issue Done in https://github.com/stylelint/stylelint/issues/7449.

I believe it's still up for discussion, especially if we're considering moving to a flat config.

Let's add [Vitest](https://vitest.dev/) to our investigation. It has a comparable API to Jest, but may offer better support for ESM. I also believe it uses ESBuild under the hood to...

I may be wrong, but I don't think we can safely merge ems into px as people can change the initial value of font-size in their browser settings. For example,...

That's correct.

(@Mouvedia [label conventions](https://stylelint.io/maintainer-guide/issues) - we typically remove the `status: need *` label when we've agreed on a cause of action.)