James Yeoman

ESLint 9 makes the flat config the default. It renames the ESLintRC style classes to be `LegacyESLint` and the Linter requires an option of `{configType: "eslintrc"}`, and in ESLint 10,...

Is there any update on this yet? Or is this still quite far off? The first release candidate for v9 released last week

Actually, the change seems to have been introduced in 0.5.6

> Actually, the change seems to have been introduced in 0.5.6 I figured out where the problem got introduced, but there's been no addressing of it thus far

This line looks like it might be the root of the issue. https://github.com/fi3ework/vite-plugin-checker/commit/8dd49159bddd7e3e23dfa479323322808094d8b9#diff-7c457428fc11687ac503085166d754dc2dbdaa3df69069d3027272bda149ba5cR189 I found that while trawling through the diff between v0.5.5 and 0.5.6 https://github.com/fi3ework/vite-plugin-checker/compare/vite-plugin-checker%400.5.5...vite-plugin-checker%400.5.6

So the logger comes from Vite itself. I wonder why this plugin isn't receiving the logger from Vite... https://github.com/fi3ework/vite-plugin-checker/commit/8dd49159bddd7e3e23dfa479323322808094d8b9

Ok, so vite-plugin-checker _is_ receiving the logger from vite, I'm just a dunce... The _actual_ problem, is that `Checker.logger` is never populated, and the colouring of diagnostics and summaries are...

As a workaround, I've got a fork that I've added a bypass to in order to avoid erroring on an empty summary. It's not the cleanest, but it allows me...

:/ I use yarn and so can't reference the fork since this plugin uses pnpm... guess I'm back to using yarn patches instead...

The problem here is that serverless-esbuild is assuming a CJS environment. However, I'm in the process of migrating to ESLint Flat Config, and so I've upgraded from v0.3.3 of `esbuild-plugin-eslint`...