Masafumi Koba

Sorry for leaving the PR for a while. I've lost interest in adding the feature, so I'm sorry but closing it. Feel free to reopen it or use a part...

@Supriya-48 Yes, please feel free to open a pull request. Nobody works on this issue now.

@ota-meshi Thanks for the share. That's an interesting trick! I now understand well what we need for running Stylelint on browsers.

@sidverma32 Thank you! Nobody currently works on this issue, so please feel free to create a pull request.

@sidverma32 To support the `--globby-options` CLI flag, we need to change `lib/cli.js` and pass the new flag value to `standalone()`: https://github.com/stylelint/stylelint/blob/7fbf2972a3c0d3d0d837fe2ba7964478fc323b7a/lib/cli.js#L506 `lib/standalone.js` has allowed the `globbyOptions` option: https://github.com/stylelint/stylelint/blob/7fbf2972a3c0d3d0d837fe2ba7964478fc323b7a/lib/standalone.js#L52

I mean: ```js if (cli.flags.globbyOptions) { optionBase.globbyOptions = cli.flags.globbyOptions; } ```

I now reconsider this issue. ### `--no-stylelintrc` Users can specify not only `.stylelintrc*` but also `stylelint.config.*` files. Additionally, they can use the [`--config`](https://stylelint.io/user-guide/usage/cli#--config) flag to specify any file. So I'm...

Reconsidering this issue's original motivation, it seems that the following option would be just required: ```shell # Run with only rules defined in an existing config file (e.g. .stylelintrc.js) stylelint...

@d-fischer Since we've decided to drop Node.js 12 support with the next major version (see #6409), I believe there is no problem that cosmiconfig drops Node.js 12 support.

When I've finished reading ESLint's [blog post](https://eslint.org/blog/2022/08/new-config-system-part-1/) about its new config system, I start doubting if this issue's flexible shorthand feature is really necessary. Because it seems to me that...