Fix Vercel deployment: add Next.js config and update build configuration

[Copilot]

Vercel deployment was failing due to missing next.config.js and incorrect build configuration treating the project as a static site instead of a Next.js application.

Changes

• Created next.config.js: CommonJS export with reactStrictMode: true
• Updated package.json scripts: Replaced http-server commands with Next.js CLI commands (next dev, next build, next start)
• Fixed vercel.json: Added version: 2, corrected headers source pattern from (.*) to /(.*)

// next.config.js
const nextConfig = {
  reactStrictMode: true,
}

module.exports = nextConfig

// vercel.json
{
  "version": 2,
  "builds": [
    {
      "src": "next.config.js",
      "use": "@vercel/next"
    }
  ],
  "headers": [
    {
      "source": "/(.*)",
      "headers": [...]
    }
  ]
}

Vercel will now detect the Next.js project and build correctly using the @vercel/next builder.

Original prompt

The Vercel deployment is failing due to a misconfigured vercel.json and incompatible package.json scripts. To fix this, follow these steps:

1. Create a valid next.config.js at the project root. Set reactStrictMode: true and export default config in CommonJS format.
2. Update package.json scripts block:
   • "dev": "next dev"
   • "build": "next build"
   • "start": "next start"
     Remove any static site or http-server scripts from the root scripts block.
3. Update vercel.json:
   • Add "version": 2 at top level.
   • Ensure "builds" uses src: "next.config.js" and use: "@vercel/next".
   • Change "headers" source to "/(.*)" (leading slash).
   • Move security headers under "headers" with correct source.
   • Remove any unused or legacy config fields like "routes".
4. Do not touch smart contract deployment scripts or monorepo subfolders, this PR only fixes the Next.js Vercel deployment root setup.

The PR should contain changes to next.config.js (add new), package.json (fix scripts), vercel.json (fix config).

After merging, Vercel should be able to detect and build the Next.js app without deployment error.

This pull request was created from Copilot chat.

---

✨ 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	Review	Updated (UTC)
aetheron	Ready	Preview, Comment	Jan 15, 2026 5:31am
vercel-node-app-1	Ready	Preview, Comment	Jan 15, 2026 5:31am

[cloudflare-workers-and-pages]

Deploying aetheron-platform with    Cloudflare Pages

Latest commit:	130615b
Status:	🚫  Build failed.

View logs

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	aetheron	130615b	Jan 15 2026, 05:30 AM

[MastaTrill]

@copilot Detect the Next.js project via next.config.js
Install dependencies (including Next.js 14.0.0)
Run npm run build (which executes next build)
Deploy the built Next.js application with the configured security headers