Pelle Wessman

I’m +1 to generate types for this module

@jeromy-cannon I'm spending my time over at https://github.com/neostandard/neostandard now – it works great with latest eslint-plugin-n and I won't personally do any work on standard here until we hopefully reconcile...

I'll let eg. @wesleytodd chime in on some of the use cases, but some quick replies: > Is there a reason you don't just write your own CLI using the...

> one way to avoid changes to the `eslint` implementation could be to add support for a standard (not `standard`, just the normal meainging of that word) cli api that...

@fregante I think @wesleytodd described the wish better: > I can say confidently that removing the config file boilerplate from application and library repos is the best way **to avoid...

> `shared-config-options` would already be too much Thinking about this further, `shared-config-options` would be completely unnecessary as any configuration needed could be achieved by eg: * Publish multiple config files...

> When it comes to the fact that eg the VSCode extension doesn't use the CLI: If it has implemented its own config resolution mechanism in such a way that...

Enabling `"eslint-preset": "neostandard"` could essentially entail modifying [`findFlatConfigFile()`](https://github.com/eslint/eslint/blob/c69b40667a288bed1290b34b37387dc671295bb0/lib/eslint/eslint.js#L273-L287) to look something like this (**rough**) sketch: ```js async function findFlatConfigFile(cwd, hasUnstableTSConfigFlag) { const filenames = hasUnstableTSConfigFlag ? FLAT_CONFIG_FILENAMES_WITH_TS : FLAT_CONFIG_FILENAMES; const...

There is prior art for such a `"eslint-preset": "neostandard"` by the way (https://github.com/neostandard/neostandard/issues/4#issuecomment-2054110916) For [`standard-engine`](https://github.com/standard/standard-engine?tab=readme-ov-file#editor-integrations) based solutions there's: ```json "standard-engine": "pocketlint" ```

An alternative solution that could be even better would be to modify `locateConfigFileToUse` instead. By both adding support for module specifiers in `--config` by using the [`resolve-from`](https://www.npmjs.com/package/resolve-from) module to do...