chore: migrate ESLint Configuration to the new flat config format #8482
chore: migrate ESLint Configuration to the new flat config format #8482
Conversation
|
💖 Thanks for opening this pull request! 💖 |
|
@zkochan Hi! I'm not familiar with the pnpm CI, not sure why the audit check is not passing, anything I can do to help fix? |
|
There are some issues with the npm registry. That's why audit failed. |
|
@zkochan Alright, any changes you'd want on this PR? For example upgrading the eslint deps (eslint v9, etc.) but feel like it would be better in a separate PR. |
|
@zkochan Maybe the eslint config needs a deeper update, to ensure it also lints Also the shared config used by the pnpm repo ( |
|
@zkochan I can make additional changes to move to https://github.com/neostandard/neostandard which seems to be the spirit of the current configuration, would that be ok with you? |
|
NB: this would be more changes since neostandard is specifying eslint v9, which is not currently supported by eslint-plugin-import |
|
Congrats on merging your first pull request! 🎉🎉🎉 |
After the migration I'm getting the exact same output from
pnpm run lint:tsthan the main branch.Warning: eslint needs Node.js with version
^18.18.0, ^20.9.0, or >=21.1.0. Main branch version is currently18.12.0mainbranch:this pr: