From eeb413e3aad53922227beedf2af092c179b15ece Mon Sep 17 00:00:00 2001 From: Roo Code Date: Wed, 4 Mar 2026 11:18:58 +0000 Subject: [PATCH] fix: add turbopack root and webpack extensionAlias to web-evals next config Workspace packages (@roo-code/types, @roo-code/ipc, @roo-code/cloud) use NodeNext module resolution with .js extensions in TypeScript imports. Without proper bundler config, these resolve to literal .js files instead of the actual .ts source files, causing "Module not found" errors. - Add turbopack.root pointing to monorepo root (matching web-roo-code) - Add webpack resolve.extensionAlias to map .js -> .ts/.tsx for builds Fixes #11853 --- apps/web-evals/next.config.ts | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/apps/web-evals/next.config.ts b/apps/web-evals/next.config.ts index b5f54a87be8..8faaff9c152 100644 --- a/apps/web-evals/next.config.ts +++ b/apps/web-evals/next.config.ts @@ -1,7 +1,20 @@ +import path from "path" import type { NextConfig } from "next" const nextConfig: NextConfig = { - turbopack: {}, + turbopack: { + root: path.join(__dirname, "../.."), + }, + webpack: (config) => { + // Enable .js -> .ts/.tsx resolution for workspace packages using NodeNext + // module resolution (e.g. @roo-code/types, @roo-code/ipc, @roo-code/cloud) + config.resolve.extensionAlias = { + ".js": [".ts", ".tsx", ".js", ".jsx"], + ".mjs": [".mts", ".mjs"], + ".cjs": [".cts", ".cjs"], + } + return config + }, } export default nextConfig