Issue with "@" Path Alias in Turborepo Build Causing Module Not Found Error #10270

Patricia-Patch · 2025-04-02T13:03:28Z

Patricia-Patch
Apr 2, 2025

Summary

I'm using a Turborepo monorepo setup where my UI package's tsconfig.json defines path aliases. When I configure the alias as "@rhu-ii/ui/*": ["./src/*"] and update my component import to:

import { cn } from '@rhu-ii/ui/lib/utils'

the build runs successfully. However, if I change the alias in tsconfig.json to "@/*": ["./src/*"] and update the import accordingly:

import { cn } from '@/lib/utils'

I get a build error:

bun run build
$ turbo run build
turbo 2.4.4

 WARNING  Unable to calculate transitive closures: No lockfile entry found for 'typescript@5.8.2'
• Packages in scope: @rhu-ii/eslint, @rhu-ii/prettier, @rhu-ii/tailwind, @rhu-ii/typescript, @rhu-ii/ui, docs, web
• Running build in 7 packages
• Remote caching disabled
┌ docs#build > cache miss, executing ea08ab36ba3c7112
│ $ next build
│    ▲ Next.js 15.2.4
│
│    Creating an optimized production build ...
└────>
┌ web#build > cache miss, executing 164309d43cdea666
│ $ next build
│    ▲ Next.js 15.2.4
│
│    Creating an optimized production build ...
│ Failed to compile.
│
│ ../../packages/ui/src/components/button.tsx
│ Module not found: Can't resolve '@/src/lib/utils'
│
│ https://nextjs.org/docs/messages/module-not-found
│
│ Import trace for requested module:
│ ./app/page.tsx
│
│
│ > Build failed because of webpack errors
│ error: script "build" exited with code 1
│
│ command finished with error: command (C:\Users\craft\Desktop\Dev\rhu-ii\apps\web) C:\Users\craft\.bun\
│ bin\bun.exe run build exited (1)
└────>
  × Internal errors encountered: unable to determine why task exited

error: script "build" exited with code 1

Here's my tsconfig.json of my packages/ui

{
  "extends": "@rhu-ii/typescript/internal-library.json",
  "compilerOptions": {
    "jsx": "preserve",
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "include": ["src"],
  "exclude": ["node_modules"]
}

And here's my internal-library.json

{
  "$schema": "https://json.schemastore.org/tsconfig",
  "extends": "./base.json",
  "compilerOptions": {
    "outDir": "${configDir}/dist",
    "module": "Preserve",
    "moduleResolution": "Bundler"
  }
}

And here's my package.json of my packages/ui

{
  "name": "@rhu-ii/ui",
  "version": "0.0.0",
  "private": true,
  "exports": {
    "./lib/*": "./src/lib/*.ts",
    "./components/*": "./src/components/*.tsx",
    "./hooks/*": "./src/hooks/*.ts"
  },
  "scripts": {
    "ui-add": "bunx --bun shadcn@latest add",
    "postui-add": "prettier src --write --list-different",
    "lint": "eslint . --max-warnings 0",
    "generate:component": "turbo gen react-component",
    "check-types": "tsc --noEmit",
    "clean": "git clean -xdf .cache .turbo node_modules"
  },
  "devDependencies": {
    "@rhu-ii/eslint": "*",
    "@rhu-ii/typescript": "0.0.0",
    "@rhu-ii/prettier": "*",
    "@rhu-ii/tailwind": "*",
    "@turbo/gen": "^2.4.4",
    "@types/node": "^22.13.10",
    "@types/react": "19.0.12",
    "@types/react-dom": "19.0.4",
    "eslint": "^9.23.0",
    "typescript": "^5.8.2"
  },
  "dependencies": {
    "@hookform/resolvers": "^5.0.1",
    "@radix-ui/react-accordion": "^1.2.3",
    "@radix-ui/react-alert-dialog": "^1.1.6",
    "@radix-ui/react-aspect-ratio": "^1.1.2",
    "@radix-ui/react-avatar": "^1.1.3",
    "@radix-ui/react-checkbox": "^1.1.4",
    "@radix-ui/react-collapsible": "^1.1.3",
    "@radix-ui/react-context-menu": "^2.2.6",
    "@radix-ui/react-dialog": "^1.1.6",
    "@radix-ui/react-dropdown-menu": "^2.1.6",
    "@radix-ui/react-hover-card": "^1.1.6",
    "@radix-ui/react-label": "^2.1.2",
    "@radix-ui/react-menubar": "^1.1.6",
    "@radix-ui/react-navigation-menu": "^1.2.5",
    "@radix-ui/react-popover": "^1.1.6",
    "@radix-ui/react-progress": "^1.1.2",
    "@radix-ui/react-radio-group": "^1.2.3",
    "@radix-ui/react-scroll-area": "^1.2.3",
    "@radix-ui/react-select": "^2.1.6",
    "@radix-ui/react-separator": "^1.1.2",
    "@radix-ui/react-slider": "^1.2.3",
    "@radix-ui/react-slot": "^1.1.2",
    "@radix-ui/react-switch": "^1.1.3",
    "@radix-ui/react-tabs": "^1.1.3",
    "@radix-ui/react-toggle": "^1.1.2",
    "@radix-ui/react-toggle-group": "^1.1.2",
    "@radix-ui/react-tooltip": "^1.1.8",
    "class-variance-authority": "^0.7.1",
    "clsx": "^2.1.1",
    "cmdk": "^1.1.1",
    "date-fns": "^4.1.0",
    "embla-carousel-react": "^8.5.2",
    "input-otp": "^1.4.2",
    "lucide-react": "^0.487.0",
    "next-themes": "^0.4.6",
    "react": "^19.1.0",
    "react-day-picker": "8.10.1",
    "react-dom": "^19.1.0",
    "react-hook-form": "^7.55.0",
    "react-resizable-panels": "^2.1.7",
    "recharts": "^2.15.1",
    "sonner": "^2.0.3",
    "tailwind-merge": "^3.1.0",
    "vaul": "^1.1.2",
    "zod": "^3.24.2"
  },
  "prettier": "@rhu-ii/prettier"
}

This error occurs during the Next.js build in the web app.
Can anyone explain why this happens and suggest a solution?

Additional information

No response

Example

No response

Answered by anthonyshew

Apr 4, 2025

Explained here: https://turbo.build/repo/docs/guides/tools/typescript#use-nodejs-subpath-imports-instead-of-typescript-compiler-paths

View full answer

anthonyshew · 2025-04-04T03:05:47Z

anthonyshew
Apr 4, 2025
Maintainer

Explained here: https://turbo.build/repo/docs/guides/tools/typescript#use-nodejs-subpath-imports-instead-of-typescript-compiler-paths

1 reply

stevegreco Apr 11, 2025

Are there any examples of this in practice? This seems to not really work well in a monorepo environment. For example, if my packages/ui has a subpath import setup. Inside that package, it is using JIT code and not the compiled components, but anything in apps/* is using compiled code.

This results in it working during development, but when you try to build anything that is using compiled code, it doesn't know how to resolve the module in dist/*.

louie337 · 2025-05-03T03:59:58Z

louie337
May 3, 2025

I came across with this page by having the same issue while trying to build my monorepo react router app in docker.

After hours of effort, finding out my problem was never about path resolving, but rather the output of turbo prune.
Once I ran turbo prune [my-app], the lib folder is actually gone in the output, which is not alias or path resolving issue.

Solution: I fixed it by renaming the lib directory generated from shadcn to library, together with all the import code & components.json. Then the build issue is gone, hope it would help someone.

1 reply

anthonyshew May 3, 2025
Maintainer

Can you file an Issue with a reproduction for this?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Issue with "@" Path Alias in Turborepo Build Causing Module Not Found Error #10270

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Issue with "@" Path Alias in Turborepo Build Causing Module Not Found Error #10270

Uh oh!

Patricia-Patch Apr 2, 2025

Summary

Additional information

Example

Replies: 2 comments · 2 replies

Uh oh!

anthonyshew Apr 4, 2025 Maintainer

Uh oh!

stevegreco Apr 11, 2025

Uh oh!

Uh oh!

louie337 May 3, 2025

Uh oh!

anthonyshew May 3, 2025 Maintainer

Patricia-Patch
Apr 2, 2025

Replies: 2 comments 2 replies

anthonyshew
Apr 4, 2025
Maintainer

louie337
May 3, 2025

anthonyshew May 3, 2025
Maintainer