mirror of
https://github.com/THU-MAIC/OpenMAIC.git
synced 2026-10-19 05:49:27 +08:00
Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: wyuc <wang-yc24@mails.tsinghua.edu.cn>
53 lines
2.1 KiB
TypeScript
53 lines
2.1 KiB
TypeScript
import type { NextConfig } from 'next';
|
|
|
|
const nextConfig: NextConfig = {
|
|
output: process.env.VERCEL ? undefined : 'standalone',
|
|
typescript: {
|
|
tsconfigPath: process.env.NODE_ENV === 'production' ? 'tsconfig.build.json' : 'tsconfig.json',
|
|
},
|
|
transpilePackages: ['mathml2omml', 'pptxgenjs', '@openmaic/importer'],
|
|
// These agent packages do a runtime `import(specifier)` with a computed
|
|
// specifier (to lazily load node:fs/os/path without breaking browser/Vite
|
|
// builds). webpack can't statically analyze that and bundling it throws
|
|
// "Cannot find module as expression is too dynamic" at runtime on the server
|
|
// (the "Edit with AI" Pro-mode path), which broke the #619 keep-alive e2e.
|
|
// Mark them server-external so Next loads them natively and the dynamic
|
|
// import resolves as a real Node call.
|
|
serverExternalPackages: [
|
|
'@earendil-works/pi-ai',
|
|
'@earendil-works/pi-agent-core',
|
|
'@openmaic/generation',
|
|
// Optional peers of @openmaic/storage, reached through deliberately
|
|
// untraced dynamic imports. Externalizing keeps them out of the bundle,
|
|
// and the static anchor in lib/persistence/asset-byte-store.ts gets them
|
|
// traced into the standalone image -- without it, S3 mode and redirect
|
|
// egress cannot resolve their SDK in the shipped deployment.
|
|
'@aws-sdk/client-s3',
|
|
'@aws-sdk/s3-request-presigner',
|
|
],
|
|
experimental: {
|
|
proxyClientMaxBodySize: '200mb',
|
|
},
|
|
async headers() {
|
|
const extraAncestors = process.env.ALLOWED_FRAME_ANCESTORS?.trim();
|
|
const frameAncestors = extraAncestors ? `'self' ${extraAncestors}` : "'self'";
|
|
|
|
return [
|
|
{
|
|
source: '/(.*)',
|
|
headers: [
|
|
// X-Frame-Options only supports SAMEORIGIN (no allow-list),
|
|
// so we omit it when custom ancestors are configured.
|
|
...(!extraAncestors ? [{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }] : []),
|
|
{
|
|
key: 'Content-Security-Policy',
|
|
value: `frame-ancestors ${frameAncestors}`,
|
|
},
|
|
],
|
|
},
|
|
];
|
|
},
|
|
};
|
|
|
|
export default nextConfig;
|