openclaw/apps/web/next.config.ts
kumarabhirup 1651b95886
chore(web): document client fallback rationale in webpack config
Clarify why browser bundles stub Node-only html-to-docx dependencies in Next.js.
2026-03-04 11:07:58 -08:00

50 lines
1.5 KiB
TypeScript

import type { NextConfig } from "next";
import path from "node:path";
import { homedir } from "node:os";
const nextConfig: NextConfig = {
// Produce a self-contained standalone build so npm global installs
// can run the web app with `node server.js` — no npm install or
// next build required at runtime.
output: "standalone",
// Required for pnpm monorepos: trace dependencies from the workspace
// root so the standalone build bundles its own node_modules correctly
// instead of resolving through pnpm's virtual store symlinks.
outputFileTracingRoot: path.join(import.meta.dirname, "..", ".."),
// Externalize packages with native addons so webpack doesn't break them
serverExternalPackages: ["ws", "bufferutil", "utf-8-validate"],
// Transpile ESM-only packages so webpack can bundle them
transpilePackages: ["react-markdown", "remark-gfm"],
webpack: (config, { dev, isServer }) => {
if (!isServer) {
// html-to-docx references Node-only modules that should not be resolved in browser bundles.
config.resolve.fallback = {
...config.resolve.fallback,
fs: false,
encoding: false,
};
}
if (dev) {
config.watchOptions = {
...config.watchOptions,
ignored: [
"**/node_modules/**",
"**/.git/**",
"**/dist/**",
"**/.next/**",
path.join(homedir(), ".openclaw", "**"),
path.join(homedir(), ".openclaw-*", "**"),
],
poll: 1500,
};
}
return config;
},
};
export default nextConfig;