build: simpler eslint config (no custom babel)

[ccorda]

See parent issue for a bit more. Leaning on next configs vs. specifying our own.

closes #184

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/patronage/bubs-next/GrRMTfUc1hfSm9Y2GkZB6HBmsJhu
✅ Preview: https://bubs-next-git-184-babel-patronage.vercel.app

[kylehotchkiss]

LGTM but one thought, should we just use the eslint that the upstream Next package requires? Or does Next.js want to see Eslint loaded in our package.json in order to activate it?

[ccorda]

I think it installs it:

If either of the two configuration options are selected, Next.js will automatically install eslint and eslint-config-next as development dependencies in your application and create an .eslintrc.json file in the root of your project that includes your selected configuration.

[ccorda]

Confirmed in a sandbox that a default next install adds the following:

package.json:

  "devDependencies": {
    "eslint": "8.5.0",
    "eslint-config-next": "12.0.7"
  }

.eslintrc.json

{
  "extends": "next/core-web-vitals"
}