eslint-formatter-pretty

I'd like to propose using the iTerm workaround also for the VSCode terminal. Maybe I am missing something, but the current implementation doesn't work for me in VSCode. If you like, I could also simplify the condition branches, as the fallback is also identical.

Environment Node.js: 22.19.0 (LTS) pnpm: 10.17.1 (pnpm’s isolated layout causes the issue) eslint: 9.36.0 @eslint/js: 9.36.0 eslint-formatter-pretty: 6.0.1 typescript: 5.9.2 Observed behavior When using ESLint config helpers such as , TypeScript reports type errors related to . The errors come from ESLint’s type definitions, not from the user’s code. Expected behavior With ESLint 9.x and , should type-check correctly without mismatches. Possible cause currently has a production dependency on , that version appears to be incompatible with ESLint 9.x. The issue disappears if the project explicitly installs the latest , overriding the version pulled in by . Suggested solutions Update the dependency to a version compatible with ESLint 9.x. Or, since eslint is shipping types with the main package - remove it in favor of optional peer dependency Steps to reproduce See reproduction repo: link here

In iTerm, Command-click the filename header to open the file in your editor. What led to this being iTerm only? Should/could the header/filename be a hyperlink itself? (a link) _Note: I am new to terminal hyperlinks and am just exploring file links, including line and column placement, so maybe iTerm’s features are better than others. I recently switched to Kitty._