Fix build: externalize elysia packages, use standalone output, fix NODE_ENV
- Add serverExternalPackages for @elysiajs/static and elysia to prevent webpack from bundling dynamic imports that cause Html prerender error - Use output: standalone for proper Docker deployment - Comment out NODE_ENV=development in .env.example to avoid conflict with next build which requires NODE_ENV=production - Set NODE_ENV=production before build step in Dockerfile - Update runtime stage to use standalone output structure Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,6 +1,8 @@
|
||||
import type { NextConfig } from "next";
|
||||
|
||||
const nextConfig: NextConfig = {
|
||||
output: 'standalone',
|
||||
serverExternalPackages: ['@elysiajs/static', 'elysia'],
|
||||
experimental: {},
|
||||
allowedDevOrigins: [
|
||||
"http://192.168.1.82:3000", // buat akses dari HP/device lain
|
||||
|
||||
Reference in New Issue
Block a user