Nitin Kumar

@alexander-akait Yeah, this could be a potential breaking change. I believe we should consider this change for webpack v6

I think we need to run `yarn special-lint-fix` here https://github.com/webpack/webpack/blob/4ba225225b1348c8776ca5b5fe53468519413bc0/package.json#L158

Thanks for the report, actually we auto-generate these links (since https://github.com/eslint/eslint/pull/16213), and the logic seems to be pointing to the `main` branch regardless of the eslint version. https://github.com/eslint/eslint/blob/bde51055530d4a71bd9f48c90ed7de9c0b767d86/docs/src/_data/sites/en.yml#L116-L118 https://github.com/eslint/eslint/blob/bde51055530d4a71bd9f48c90ed7de9c0b767d86/docs/src/_includes/layouts/doc.html#L99-L108 So...

I'm unsure if this is a bug or a limitation for our docs. We can provide edit links only for branches that exist, however for published releases we [maintain tags...

I'll give this a shot.

I can look into it, but it will take some time as I am not familiar with this repo and the GitHub API.

I'm fine with this enhancement, should be easy.

The path below is indeed incorrect and needs to be updated. https://github.com/eslint/eslint/blob/15c143f96ef164943fd3d39b5ad79d9a4a40de8f/packages/js/src/configs/eslint-recommended.js#L11 Good catch, this seems like it was missed in https://github.com/eslint/eslint/pull/16844 @colireg Would you like to send a PR?

>Since this is a separate package, it probably shouldn't be using a relative path to a module that isn't in the package? Yes, we may need to copy this type...

Yes, we can just remove this line.