Resolve eslint-config-next@16.0.10 peer dependency conflict

[Copilot]

The dependabot upgrade to eslint-config-next@16.0.10 failed deployment due to peer dependency mismatch: it requires eslint@>=9.0.0 but the project had eslint@8.57.0.

Changes

• Upgraded ESLint: ^8 → ^9 to satisfy peer dependency
• Upgraded Next.js: ^14.2.24 → 16.0.10 (required for ESLint 9 compatibility)
• Migrated to ESLint 9 flat config:
  • Created eslint.config.mjs with flat config format
  • Removed deprecated .eslintrc.json
• Updated lint script: next lint → eslint . (Next.js 16 removed the lint command)

ESLint Configuration Migration

ESLint 9 requires flat config format. Old .eslintrc.json:

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

New eslint.config.mjs:

import nextConfig from 'eslint-config-next/core-web-vitals';

export default nextConfig;

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
dayif-portfolio	Error			Dec 12, 2025 9:19am

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/dayif-portfolio/dayif-portfolio/node_modules/.bin/next build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)