Fix GitHub Actions workflow - replace Webpack with Next.js build

[Copilot]

The deployment workflow was failing because it attempted to run npx webpack on a Next.js project, causing interactive webpack-cli installation prompts and build failures.

Changes

• Workflow configuration (.github/workflows/webpack.yml → nextjs-build.yml)

  • Replace npx webpack with npm run build
  • Add npm caching via actions/setup-node@v4
  • Use npm ci instead of npm install for deterministic builds
  • Add explicit permissions: contents: read

• Dependencies (package.json)

  • Add missing @radix-ui/react-radio-group (required by components/ui/radio-group.tsx)

• ESLint (.eslintrc.json)

  • Add next/core-web-vitals config to prevent interactive prompts

# Before
- name: Build
  run: |
    npm install
    npx webpack

# After  
- name: Build
  run: |
    npm ci
    npm run build

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: node /home/REDACTED/work/v0-memorialqrwebsitecode/v0-memorialqrwebsitecode/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)

Original prompt

Fix the deployment issues

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
v0-deal-patrol-v0-memorialqrwebsite	Error			Nov 1, 2025 5:44am
v0-memorialqrwebsitecode-90	Ready	Preview	Comment	Nov 1, 2025 5:44am