Next.js on Exovon

Navigate to the Exovon Dashboard, click New Project, and select your Next.js repository. Exovon automatically inspects your package.json and detects Next.js.

Paste your .env or .env.local variables into the Bulk Importer. Secrets are stored with envelope encryption (AES-256 GCM) and validated during pre-flight checks to prevent failed builds.

Click Deploy. Exovon triggers a dedicated build worker (e2-standard-4: 4 vCPUs, 16 GB RAM) in Mumbai, builds your app in seconds, and spins up your production container with an automatic .exovon.co.in SSL domain.

1. Enable Standalone Output in Next Config

Add output: 'standalone' to your next.config.js or next.config.ts. This produces a minimal self-contained server package that significantly reduces container build times and RAM consumption:

// next.config.ts
import type { NextConfig } from 'next';

const nextConfig: NextConfig = {
  output: 'standalone',
  images: {
    formats: ['image/avif', 'image/webp'],
  },
};

export default nextConfig;

2. Wrap useSearchParams() in <React.Suspense>

In Next.js 14 and 15 App Router, any client component accessing URL search parameters via useSearchParams() should be wrapped in a <Suspense> boundary. This allows static generation to prerender the page skeleton without bailing out:

import { Suspense } from 'react';
import SearchableClientComponent from './search-box';
import SkeletonLoader from './skeleton';

export default function Page() {
  return (
    <Suspense fallback={<SkeletonLoader />}>
      <SearchableClientComponent />
    </Suspense>
  );
}

3. Database Connection Pooling (Prisma / Drizzle)

Because Exovon runs in Mumbai (asia-south1), you can connect directly to PostgreSQL, MySQL, Supabase, Neon, or Cloud SQL instances in India. For high-traffic workloads, instantiate your database client as a singleton or use a connection pooler (e.g. PgBouncer) to prevent connection exhaustion during autoscaling surges.