Next.js Static Export Tips and Architecture Boundaries

Next.js defaults to a dynamic server-rendered runtime. However, for portfolios and serverless deployments like Polimelo, compilation to static assets via output: 'export' is highly cost-effective and performs exceptionally fast on global CDNs.

Static Export Trade-offs

Node.js runtime server features (like Middleware, dynamic runtime headers, or runtime API endpoints) are not supported. Every page route must resolve to HTML pages at build-time. For dynamic paths, this means utilizing generateStaticParams() to pre-render all URLs.

Handling Client Parameters

Since URL search queries (like ?id=123) are unavailable during static HTML compilation, you must handle them on the client side. Accessing query states via useSearchParams within wrapper Client Components is the standard practice.