Pelle Wessman

I had totally missed that an entirely new config lookup was in the progress, https://github.com/eslint/eslint/pull/18742, so I guess those investigations of me above is good for nothing else than clarifying...

> You discussed a lot of stuff in the previous comments I have tried to look into where a `"eslint-preset": "neostandard"` resolution could happen, to see if its feasible. This...

@nzakas That's the exact reason why I split the proposal into two distinct parts, so that the objection against one wouldn't necessitate the object of the other, and your objection...

@nzakas And the main proposal? This one: > 1. Enable an equivalent to the `--config` CLI option to be specified in a declarative way that editor extensions etc can discover...

@nzakas Again – that’s not the proposal – this is: > Enable an equivalent to the `--config` CLI option to be specified in a declarative way that editor extensions etc...

> this thread hasn't been the easiest to follow Yeah, there hasn’t been a very collaborative response so I have had to guess a lot and have had try to...

@fregante So `xo` will ditch the `xo` command and only use `eslint-config-xo` through `eslint.config.js` going forward? Or `xo` will continue to maintain `xo` as a separate ecosystem? --- I’m not...

A fourth idea (that I don’t really like) would be to suggest a new naming scheme, eg: `eslint-preset-neostandard` And the presence of such a one in the dependencies would auto-configure...

Been looking at how this can interact with the `avvio` core as well, automatically adding the methods on `register` and eg. `after` – a tricky part is that the `.use()`...

For reference, this is the docs on type narrowing that goes through type predicates, discriminated unions and links out to the blog post announcing _assertion functions_ (added in TS 3.7,...