Pelle Wessman

Would be good to get https://github.com/eslint-community/eslint-utils/issues/183 / https://github.com/eslint-community/eslint-utils/pull/186 in there as well, as it may be a blocker for quite a few other modules

What's the officially suggested peer-dependency range for someone who wants to support eg. ESLint 8 and later, including pre-releases of ESLint 9? I think the algorithm for npm is what...

Chrome is shipping it: https://developer.chrome.com/docs/capabilities/web-apis/reporting-api

* `eslint-plugin-import` has a fork over at https://github.com/un-es/eslint-plugin-import-x that may update sooner: https://github.com/un-es/eslint-plugin-import-x/issues/29 * do you mean `@eslint-community/eslint-plugin-eslint-comments` @spence-s? I'm at the Community Core team so feel free to ping...

Looks like @rossknudsen is working on bringing the current Jest Test Adapter extension up to date – maybe better to double down on that one and keeping this a separate...

I solved it like this in the @SocketDev CLI: https://github.com/SocketDev/socket-cli-js/blob/f45cbd408c0575dfe205cf968596f4506f15f44d/lib/utils/meow-with-subcommands.js#L33 Planned to extract it to its own module and might still do even though I'm no longer with Socket

Was completed

Fix by simply removing empty URL:s

Still relevant :)

I guess this still holds true: > still need to support OpenAPI 3.1 But maybe better to add that as a new issue? To make it clearer?