Update eslint dependencies.

[davidlehn]

• Use @digitalbazaar/eslint-config@7.
• Remove unneeded peer deps.
• Add globals.

[cloudflare-workers-and-pages]

Deploying canivc with    Cloudflare Pages

Latest commit:	615a96d
Status:	✅  Deploy successful!
Preview URL:	https://b02d463b.canivc.pages.dev
Branch Preview URL:	https://update-dependencies.canivc.pages.dev

View logs

[BigBlueHat]

@davidlehn looks like the globals dependency was coming in via @digitalbazaar/eslint-config and the explicit inclusion here wasn't needed. I removed it from this package.json and did an npm ci and linting ran the same as before removing it. So...am I missing something? or is it OK to remove this dependency (as I've done in 615a96d)?

[davidlehn]

eslint.config.js is using globals directly, so seemed appropriate to have it as a dependency. In this case, I'm pretty sure it will keep being an indirect dependency, but general best practice is to depend on what you use. npm-check flagged it which is why it was added.

There may be a better way to set thing up to avoid the issue in general. A special clause for those asset files seemed like a good enough approach at the time.