Version >= 3.8 causes ESLint stuck in nuxt project #356

ntnyq · 2025-02-17T20:25:27Z

Version

Since v3.8.0, v3.8.1 still have the issue.

v3.7.0 works as expected.

Reproduction repo

Steps

Run eslint --debug ., everything goes fine
Change USE_TYPESCRIPT_RESOLVER to true, and run eslint --debug . again.

ESLint will stuck at eslint:languages:js Scope analysis successful message

The text was updated successfully, but these errors were encountered:

ntnyq · 2025-02-17T20:28:03Z

Only happened in my NuxtJS project.

For other projects, it still works fine.

ntnyq · 2025-02-17T20:32:45Z

Maybe there are too much node_modules path in nuxt generated tsconfig.json file.

{
  "compilerOptions": {
    "paths": {
      "nitropack/types": [
        "../node_modules/.pnpm/[email protected][email protected]/node_modules/nitropack/types"
      ],
      "nitropack/runtime": [
        "../node_modules/.pnpm/[email protected][email protected]/node_modules/nitropack/runtime"
      ],
      "nitropack": [
        "../node_modules/.pnpm/[email protected][email protected]/node_modules/nitropack"
      ],
      "defu": [
        "../node_modules/.pnpm/[email protected]/node_modules/defu"
      ],
      "h3": [
        "../node_modules/.pnpm/[email protected]/node_modules/h3"
      ],
      "consola": [
        "../node_modules/.pnpm/[email protected]/node_modules/consola"
      ],
      "ofetch": [
        "../node_modules/.pnpm/[email protected]/node_modules/ofetch"
      ],
      "@unhead/vue": [
        "../node_modules/.pnpm/@[email protected][email protected][email protected]_/node_modules/@unhead/vue"
      ],
      "@nuxt/devtools": [
        "../node_modules/.pnpm/@[email protected][email protected][email protected]_@[email protected][email protected][email protected]_9ee0250e209ac58c719ffd43dfe4102d/node_modules/@nuxt/devtools"
      ],
      "@vue/runtime-core": [
        "../node_modules/.pnpm/@[email protected]/node_modules/@vue/runtime-core"
      ],
      "@vue/compiler-sfc": [
        "../node_modules/.pnpm/@[email protected]/node_modules/@vue/compiler-sfc"
      ],
      "unplugin-vue-router/client": [
        "../node_modules/.pnpm/[email protected][email protected][email protected][email protected][email protected][email protected][email protected]_/node_modules/unplugin-vue-router/client"
      ],
      "@nuxt/schema": [
        "../node_modules/.pnpm/@[email protected]/node_modules/@nuxt/schema"
      ],
      "nuxt": [
        "../node_modules/.pnpm/[email protected]_@[email protected]_@[email protected][email protected][email protected][email protected]._255c37df78b381005c9aaa0ce6468c22/node_modules/nuxt"
      ],
      "vite/client": [
        "../node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected][email protected]/node_modules/vite/client"
      ],
      "~": [
        ".."
      ],
      "~/*": [
        "../*"
      ],
      "@": [
        ".."
      ],
      "@/*": [
        "../*"
      ],
      "~~": [
        ".."
      ],
      "~~/*": [
        "../*"
      ],
      "@@": [
        ".."
      ],
      "@@/*": [
        "../*"
      ],
      "#shared": [
        "../shared"
      ],
      "assets": [
        "../assets"
      ],
      "public": [
        "../public"
      ],
      "#app": [
        "../node_modules/.pnpm/[email protected]_@[email protected]_@[email protected][email protected][email protected][email protected]._255c37df78b381005c9aaa0ce6468c22/node_modules/nuxt/dist/app"
      ],
      "#app/*": [
        "../node_modules/.pnpm/[email protected]_@[email protected]_@[email protected][email protected][email protected][email protected]._255c37df78b381005c9aaa0ce6468c22/node_modules/nuxt/dist/app/*"
      ],
      "vue-demi": [
        "../node_modules/.pnpm/[email protected]_@[email protected]_@[email protected][email protected][email protected][email protected]._255c37df78b381005c9aaa0ce6468c22/node_modules/nuxt/dist/app/compat/vue-demi"
      ],
      "#vue-router": [
        "../node_modules/.pnpm/[email protected][email protected][email protected]_/node_modules/vue-router"
      ],
      "#imports": [
        "./imports"
      ],
      "#app-manifest": [
        "./manifest/meta/cc5befc9-0c27-4f58-9757-ace23830319b"
      ],
      "#components": [
        "./components"
      ],
      "#build": [
        "."
      ],
      "#build/*": [
        "./*"
      ]
    },
    "esModuleInterop": true,
    "skipLibCheck": true,
    "target": "ESNext",
    "allowJs": true,
    "resolveJsonModule": true,
    "moduleDetection": "force",
    "isolatedModules": true,
    "verbatimModuleSyntax": true,
    "strict": true,
    "noUncheckedIndexedAccess": false,
    "forceConsistentCasingInFileNames": true,
    "noImplicitOverride": true,
    "module": "preserve",
    "noEmit": true,
    "lib": [
      "ESNext",
      "dom",
      "dom.iterable",
      "webworker"
    ],
    "jsx": "preserve",
    "jsxImportSource": "vue",
    "types": [],
    "moduleResolution": "Bundler",
    "useDefineForClassFields": true,
    "noImplicitThis": true,
    "allowSyntheticDefaultImports": true
  },
  "include": [
    "./nuxt.d.ts",
    "../.config/nuxt.*",
    "../**/*",
    "../node_modules/.pnpm/@[email protected][email protected][email protected]_@[email protected][email protected][email protected]_9ee0250e209ac58c719ffd43dfe4102d/node_modules/@nuxt/devtools/runtime",
    "../node_modules/.pnpm/@[email protected][email protected][email protected]_@[email protected][email protected][email protected]_9ee0250e209ac58c719ffd43dfe4102d/node_modules/@nuxt/devtools/dist/runtime",
    "../node_modules/.pnpm/@[email protected][email protected]/node_modules/@nuxt/telemetry/runtime",
    "../node_modules/.pnpm/@[email protected][email protected]/node_modules/@nuxt/telemetry/dist/runtime",
    ".."
  ],
  "exclude": [
    "../dist",
    "../node_modules",
    "../node_modules/.pnpm/[email protected]_@[email protected]_@[email protected][email protected][email protected][email protected]._255c37df78b381005c9aaa0ce6468c22/node_modules/nuxt/node_modules",
    "../node_modules/.pnpm/@[email protected][email protected][email protected]_@[email protected][email protected][email protected]_9ee0250e209ac58c719ffd43dfe4102d/node_modules/@nuxt/devtools/node_modules",
    "../node_modules/.pnpm/@[email protected][email protected]/node_modules/@nuxt/telemetry/node_modules",
    "../node_modules/.pnpm/@[email protected][email protected][email protected]_@[email protected][email protected][email protected]_9ee0250e209ac58c719ffd43dfe4102d/node_modules/@nuxt/devtools/runtime/server",
    "../node_modules/.pnpm/@[email protected][email protected][email protected]_@[email protected][email protected][email protected]_9ee0250e209ac58c719ffd43dfe4102d/node_modules/@nuxt/devtools/dist/runtime/server",
    "../node_modules/.pnpm/@[email protected][email protected]/node_modules/@nuxt/telemetry/runtime/server",
    "../node_modules/.pnpm/@[email protected][email protected]/node_modules/@nuxt/telemetry/dist/runtime/server",
    "../.output"
  ]
}

JounQin · 2025-02-18T05:58:54Z

cc @carlocorradini

mkosir · 2025-02-18T07:40:13Z

I’m experiencing the same issue with the project react-parallax-tilt.
You can reproduce it by upgrading the dependency version to >=3.8

carlocorradini · 2025-02-18T07:42:05Z

@mkosir @ntnyq I'll try to fix it ASAP

carlocorradini · 2025-02-18T11:23:21Z

I've tried your repo on Windows with import-x/resolver-next forced to use createTypeScriptImportResolver.
Executed the command npx eslint --debug . and everything worked fine, I obtained the following correct output (added debug.enable(IMPORTER_NAME); in eslint-import-resolver-typescript source code):

eslint-import-resolver-typescript looking for typescript-eslint in [OMITTED]\eslint-import-resolver-typescript-main\eslint.config.mjs +0ms
eslint-import-resolver-typescript matched node path: [OMITTED]\eslint-import-resolver-typescript-main\node_modules\typescript-eslint\dist\index.d.ts +26ms
eslint-import-resolver-typescript looking for eslint-plugin-import-x in [OMITTED]\eslint-import-resolver-typescript-main\eslint.config.mjs +0ms
eslint-import-resolver-typescript looking for @types\eslint-plugin-import-x in [OMITTED]\eslint-import-resolver-typescript-main\eslint.config.mjs +10ms
eslint-import-resolver-typescript didn't find  @types\eslint-plugin-import-x +10ms
eslint-import-resolver-typescript matched node path: [OMITTED]\eslint-import-resolver-typescript-main\node_modules\eslint-plugin-import-x\lib\index.js +0ms
eslint-import-resolver-typescript looking for eslint-import-resolver-typescript in [OMITTED]\eslint-import-resolver-typescript-main\eslint.config.mjs +1ms
eslint-import-resolver-typescript matched node path: [OMITTED]\eslint-import-resolver-typescript-main\node_modules\eslint-import-resolver-typescript\lib\index.d.ts +6ms

Nothing blocked ESLint, any ideas?

tbastyns · 2025-02-18T13:00:09Z

We've had a similar issue where a small module that previously took 2-3 seconds to lint, suddenly started taking 30-40 seconds
We developers both use macs and suffer from this slowness. Our CI/CD pipeline, which runs on ubuntu, was not affected

At first glance, the issue looks to be resolved after bumping tinyglobby (dependency of this package) from 0.2.10 to 0.2.11 (either by messing with our lockfile, or adding it explicitly as a dependency)

If you look at the changelog of tinyglobby, they do indeed mention something about performance: https://github.com/SuperchupuDev/tinyglobby/releases/tag/0.2.11 , so it seems like a reasonable explanation. Bumping the dependency here could maybe solve the issue for other people as well :)

ntnyq · 2025-02-18T13:10:40Z

I've made a new commit to the reproduction repo.

Enabled typescript resolver add added a workflow to run lint in different os.

ESLint stuck at every os with lts/latest node add the workflow failed after 10min(timeout is set to 10min).

You can check it here

https://github.com/ntnyq-dev/eslint-import-resolver-typescript/actions/runs/13391158732

carlocorradini · 2025-02-18T13:12:45Z

@tbastyns See PR #357

carlocorradini · 2025-02-18T13:13:29Z

@ntnyq I'll retry, give me a couple of minutes... stay tuned

carlocorradini · 2025-02-18T13:41:55Z

I tried using npm and it worked. The problem occurs when using pnpm.
I'll look into it further, but does anyone have any ideas about what's causing it?

tbastyns · 2025-02-18T13:53:21Z

a possibility would be that if you do a fresh install on the provided reproduction-repo, it will now install [email protected] (as it satisfies ^2.0.10), but when using pnpm it will take into account pnpm-lock.yaml, where the version is 'pinned' to 0.2.10

or maybe tinyglobby has nothing to do with the original issue of this thread :D it's just a guess

ntnyq · 2025-02-18T14:03:35Z

Bump tinyglobby to v0.2.11 does solve the issue.

I tried in my local by adding

 "resolutions": {
    "tinyglobby": "^0.2.11"
  }

carlocorradini · 2025-02-18T14:13:58Z

PR #357 should fix the issue then 🥳
Nevertheless, I'll try with npm and tinyglobby 0.2.10

carlocorradini · 2025-02-18T14:45:56Z

I can guarantee that this problem happens in npm while using tinyglobby version 0.2.10, but not version 0.2.11.
Therefore, when PR #357 is merged the issue is fixed

carlocorradini · 2025-02-18T14:55:44Z

@SukkaW This can be closed 🥳

SukkaW · 2025-02-18T14:57:12Z

Fixed by #357 (hopefully) and included in v3.8.2.

carlocorradini mentioned this issue Feb 18, 2025

chore(deps): update tinyglobby to the latest version #357

Merged

SukkaW closed this as completed Feb 18, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Version >= 3.8 causes ESLint stuck in nuxt project #356

Version >= 3.8 causes ESLint stuck in nuxt project #356

ntnyq commented Feb 17, 2025 •

edited

Loading

ntnyq commented Feb 17, 2025

ntnyq commented Feb 17, 2025

JounQin commented Feb 18, 2025

mkosir commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

tbastyns commented Feb 18, 2025

ntnyq commented Feb 18, 2025 •

edited

Loading

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

tbastyns commented Feb 18, 2025

ntnyq commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

SukkaW commented Feb 18, 2025

Version >= 3.8 causes ESLint stuck in nuxt project #356

Version >= 3.8 causes ESLint stuck in nuxt project #356

Comments

ntnyq commented Feb 17, 2025 • edited Loading

Version

Steps

ntnyq commented Feb 17, 2025

ntnyq commented Feb 17, 2025

JounQin commented Feb 18, 2025

mkosir commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

tbastyns commented Feb 18, 2025

ntnyq commented Feb 18, 2025 • edited Loading

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

tbastyns commented Feb 18, 2025

ntnyq commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

carlocorradini commented Feb 18, 2025

SukkaW commented Feb 18, 2025

ntnyq commented Feb 17, 2025 •

edited

Loading

ntnyq commented Feb 18, 2025 •

edited

Loading