From eec8ffe2adeed87e2521855ae5ba1c8cadcfaf89 Mon Sep 17 00:00:00 2001 From: i-trytoohard Date: Tue, 19 May 2026 22:47:03 +0000 Subject: [PATCH] fix(web): externalize ao-core and better-sqlite3 from Next.js bundle MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes #1930. Next.js bundles @aoagents/ao-core (via transpilePackages) and bakes import.meta.url as the build machine's absolute path into the output. At runtime on any other machine (especially Windows), createRequire() receives a non-existent file:// URL and fails. Adding @aoagents/ao-core and better-sqlite3 to serverExternalPackages tells Next.js to not bundle these — they're resolved at runtime from node_modules, so import.meta.url resolves to the actual install path. This fixes: - events-db.ts: createRequire(import.meta.url)("better-sqlite3") - update-cache.ts: createRequire(fileURLToPath(import.meta.url)) - The Windows ERR_INVALID_ARG_VALUE error in the user report --- packages/web/next.config.js | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packages/web/next.config.js b/packages/web/next.config.js index 5923fedff..8627a965f 100644 --- a/packages/web/next.config.js +++ b/packages/web/next.config.js @@ -22,6 +22,8 @@ const nextConfig = { serverExternalPackages: [ "yaml", "zod", + "@aoagents/ao-core", + "better-sqlite3", ], webpack: (config, { isServer }) => { if (process.platform === "win32") {