ESLint import/no-unresolved on 3.7.0 when importing with @-alias

[janericwinkelmann]

Environment

• Operating System: Darwin
• Node Version: v19.3.0
• Nuxt Version: 3.7.0
• CLI Version: 3.7.3
• Nitro Version: 2.6.2
• Package Manager: npm@9.2.0
• Builder: -
• User Config: runtimeConfig, css, nitro, vite, experimental, components, app, modules, i18n, build
• Runtime Modules: @nuxtjs/tailwindcss@6.8.0
• Build Modules: -

Reproduction

Create a new nuxt project, add a new custom folder and place a js file inside. Try to import this file. Enable linting and you should be able to reproduce the error on build.

Describe the bug

Prior to Nuxt 3.7.0 this was working fine. When importing a file from a non standard root level folder with the "@"-alias we now receive a linting error on build and on lint, but not when running nuxi dev:

import fragment from '@/shaders/fragment.glsl'
or
import math from '@/lib/math.js'

On build we than receive the error:
6:20 error Unable to resolve path to module '@/shaders/fragment.glsl' import/no-unresolved

When using
import fragment from '../shaders/fragment.glsl'
instead, everything's working fine.

Additional context

No response

Logs

No response

[github-actions]

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[daspete]

Same here, no alias imports are working.

[killjoy1221]

It seems to be related to the extends paired with the generated tsconfig.json no longer having a baseDir value. My quick fix is to specify the nuxt tsconfig in the eslint settings.

// .eslintrc
{
  "settings": {
    "import/resolver": {
      "typescript": {
        "project": "./.nuxt/tsconfig.json"
      }
    }
  }
}

Possibly related: dividab/tsconfig-paths#224

[leo-buneev]

Can confirm.
Source of the issue is package get-tsconfig, which eslint-import-resolver-typescript depends on
https://github.com/privatenumber/get-tsconfig/blob/develop/src/parse-tsconfig/index.ts

here when it resolves extended config it doesn't adjust relative values in compilerOptions.paths

[danielroe]

Thanks for the debugging. This isn't a Nuxt issue, it seems, so I'm closing. But if you think there's something we should be doing, please feel free to let me know.