Upgrade eslint to version 7.30.0

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint (^5.6.0 → ^7.30.0) · Repo · Changelog

Release Notes

7.30.0

• 5f74642 Chore: don't check Program.start in SourceCode#getComments (refs #14744) (#14748) (Milos Djermanovic)
• 19a871a Docs: Suggest linting plugins for ESLint plugin developers (#14754) (Bryan Mishkin)
• aa87329 Docs: fix broken links (#14756) (Sam Chen)
• 278813a Docs: fix and add more examples for new-cap rule (fixes #12874) (#14725) (Nitin Kumar)
• ed1da5d Update: ecmaVersion allows "latest" (#14720) (薛定谔的猫)
• 104c0b5 Update: improve use-isnan rule to detect Number.NaN (fixes #14715) (#14718) (Nitin Kumar)
• b08170b Update: Implement FlatConfigArray (refs #13481) (#14321) (Nicholas C. Zakas)
• f113cdd Chore: upgrade eslint-plugin-eslint-plugin (#14738) (薛定谔的猫)
• 1b8997a Docs: Fix getRulesMetaForResults link syntax (#14723) (Brandon Mills)
• aada733 Docs: fix two broken links (#14726) (Sam Chen)
• 8972529 Docs: Update README team and sponsors (ESLint Jenkins)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 13 commits:

• 7.30.0
• Build: changelog update for 7.30.0
• Chore: don't check Program.start in SourceCode#getComments (refs #14744) (#14748)
• Docs: Suggest linting plugins for ESLint plugin developers (#14754)
• Docs: fix broken links (#14756)
• Docs: fix and add more examples for new-cap rule (fixes #12874) (#14725)
• Update: ecmaVersion allows "latest" (#14720)
• Update: improve use-isnan rule to detect `Number.NaN` (fixes #14715) (#14718)
• Update: Implement FlatConfigArray (refs #13481) (#14321)
• Chore: upgrade eslint-plugin-eslint-plugin (#14738)
• Docs: Fix getRulesMetaForResults link syntax (#14723)
• Docs: fix two broken links (#14726)
• Docs: Update README team and sponsors

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #132.