[BUG] Trying to install evals in Ubuntu, not working due to module errors

[shruthi-sh]

Problem (one or two sentences)

I am using an Ubuntu 22.04 Jammy PC. I have pulled the git repo. Running pnpm evals in the root of the repo, I am getting "Module not found" errors.
One such error:
./packages/types/src/index.ts:23:1
Module not found: Can't resolve './task.js'

export * from "./task.js"

The same error occurs for a list of files containing exports.

I am using node version 20.19.2, pnpm version 10.8.1.

Context (who is affected and when)

Happens to new users who are trying to install evals system in Ubuntu.

Reproduction steps

1. install docker, git, nvm, node, pnpm.
2. clone the evals repo
3. run "pnpm evals"

Expected result

It should start a web service

Actual result

Breaks down during build process in docker.

Variations tried (optional)

Tried changing tsconfig.json module to ESNext. It's breaking in other places where nodenext type of imports are required.

App Version

NA

API Provider (optional)

None

Model Used (optional)

N/A

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause:
The apps/web-evals/next.config.ts is missing the turbopack.root configuration that tells Next.js/Turbopack where the monorepo root is. Without this, Turbopack cannot properly resolve .js extension imports to their corresponding .ts source files in workspace packages.

Several workspace packages (@roo-code/types, @roo-code/ipc, @roo-code/cloud) use NodeNext module resolution, which requires .js extensions in TypeScript imports (e.g., export * from "./task.js"). When Turbopack does not know the monorepo root, it looks for literal .js files instead of resolving them to the actual .ts source files, causing the "Module not found" errors.

The other Next.js app in this monorepo (apps/web-roo-code) already has this fix in place and works correctly.

Proposed Fix:
Update apps/web-evals/next.config.ts to add the turbopack.root setting, matching the pattern used by apps/web-roo-code/next.config.ts:

import path from "path"
import type { NextConfig } from "next"

const nextConfig: NextConfig = {
  turbopack: {
    root: path.join(__dirname, "../.."),
  },
}

export default nextConfig

This single-line addition tells Turbopack the monorepo root is two directories up from apps/web-evals/, enabling it to properly resolve workspace package imports with .js extensions to their .ts source files.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[shruthi-sh]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause: The apps/web-evals/next.config.ts is missing the turbopack.root configuration that tells Next.js/Turbopack where the monorepo root is. Without this, Turbopack cannot properly resolve .js extension imports to their corresponding .ts source files in workspace packages.

Several workspace packages (@roo-code/types, @roo-code/ipc, @roo-code/cloud) use NodeNext module resolution, which requires .js extensions in TypeScript imports (e.g., export * from "./task.js"). When Turbopack does not know the monorepo root, it looks for literal .js files instead of resolving them to the actual .ts source files, causing the "Module not found" errors.

The other Next.js app in this monorepo (apps/web-roo-code) already has this fix in place and works correctly.

Proposed Fix: Update apps/web-evals/next.config.ts to add the turbopack.root setting, matching the pattern used by apps/web-roo-code/next.config.ts:

import path from "path"
import type { NextConfig } from "next"

const nextConfig: NextConfig = {
turbopack: {
root: path.join(__dirname, "../.."),
},
}

export default nextConfig
This single-line addition tells Turbopack the monorepo root is two directories up from apps/web-evals/, enabling it to properly resolve workspace package imports with .js extensions to their .ts source files.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

This doesn't seem to be working. Getting the same error.

[roomote-v0]

I've seen the comment and am investigating. The turbopack.root fix is part of the solution, but there may be additional config needed to handle .js -> .ts resolution in webpack builds (used by next build in some Next.js versions). I'll open a PR with a more comprehensive fix.

[roomote-v0]

Opened a draft PR with my attempt at addressing this: #11855

The fix adds both turbopack.root (for Turbopack, matching the pattern in web-roo-code) and webpack resolve.extensionAlias (to map .js -> .ts/.tsx for webpack-based builds). This covers both bundler paths that next dev and next build may use.

Feedback welcome!

[shruthi-sh]

Opened a draft PR with my attempt at addressing this: #11855

The fix adds both turbopack.root (for Turbopack, matching the pattern in web-roo-code) and webpack resolve.extensionAlias (to map .js -> .ts/.tsx for webpack-based builds). This covers both bundler paths that next dev and next build may use.

Feedback welcome!

This is still giving the same error.