Fix: Make npm install work

[nzakas]

npm install isn't working due to peer dependencies in eslint-config-eslint, which is throwing npm 7 into a rage.

This just remove eslint-config-eslint for now so we can start developing again. The real fix is to update eslint-config-eslint.

[eslint-github-bot]

Hi @nzakas!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag must be one of the following:

  The Tag is one of the following:

  • Fix - for a bug fix.
  • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
  • New - implements a new feature.
  • Breaking - for a backwards-incompatible enhancement or feature.
  • Docs - changes to documentation only.
  • Build - changes to build process only.
  • Upgrade - for a dependency upgrade.
  • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

  You can use the labels of the issue you are working on to determine the best tag.

• There should be a space following the initial tag and colon, for example 'New: Message'.

• The first letter of the tag should be in uppercase

Read more about contributing to ESLint here

[aladdin-add]

it will disable all rules in the config. can we just use npm install --force for the time being - util the issue was fixed in eslint-config-eslint?

[nzakas]

That didn’t work when I tried. I’d just like to get unblocked. We will be retiring this utility soon so I’m not too concerned if linting is unavailable for a bit.

[mdjermanovic]

We were using an old version of eslint-config-eslint, the peer deps issue has been fixed in v7.0.0.

Can we upgrade to 7.0.0 instead of removing it? I made PR #54, and it seems to work on Node 15 and Node 16.

[nzakas]

Closing in favor of #54.