Weird behavior of path define

Answered

qwrts posted this in #help-forum

2024-12-18T15:16:56.933Z

Usually, when I select to use @ for defining root path it worked

example:

import Navbar from '@/components/Navbar';

but later, this method is not working anymore. like suddenly happen out of nowhere
the build error occurred and showing module not found

Answered by joulev

yeah then that's why. copy the thing inside compilerOptions in jsconfig.json, paste it to the bottom of the compilerOptions in tsconfig.json

View full answer

14 Replies

@qwrts Usually, when I select to use `@` for defining root path it worked example: js import Navbar from '@/components/Navbar'; but later, this method is not working anymore. like suddenly happen out of nowhere the build error occurred and showing `module not found`

joulev

2024-12-18T15:18:25.176Z

could you show your tsconfig.json?

@joulev could you show your tsconfig.json?

qwrtsOP

2024-12-18T15:19:11.445Z

{
  "compilerOptions": {
    "target": "ES2017",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": false,
    "noEmit": true,
    "incremental": true,
    "module": "esnext",
    "esModuleInterop": true,
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "plugins": [
      {
        "name": "next"
      }
    ]
  },
  "include": [
    "next-env.d.ts",
    ".next/types/**/*.ts",
    "**/*.ts",
    "**/*.tsx"
  ],
  "exclude": [
    "node_modules"
  ]
}