Types of exports in `.nuxt/eslint.config.mjs` is broken with pnpm v10

[sushichan044]

Environment

---

• Operating System: Linux
• Node Version: v22.13.0
• Nuxt Version: 3.15.4
• CLI Version: 3.21.1
• Nitro Version: 2.10.4
• Package Manager: pnpm@10.2.0
• Builder: -
• User Config: compatibilityDate, devtools, modules
• Runtime Modules: @nuxt/eslint@1.0.0
• Build Modules: -

---

Package

@nuxt/eslint

Reproduction

repo: https://github.com/sushichan044/nuxt-eslint-type-broken-pnpm-v10

1. clone repo
2. setup pnpm (>=10) and install deps
3. open eslint.config.mjs
4. withNuxt and configs are treated as any by TypeScript

Describe the bug

When using pnpm v10 with @nuxt/eslint module, types of exports from .nuxt/eslint.config.mjs is broken and
we cannot get completion when editing eslint.config.js.

This is because pnpm v10 no longer hoists packages that include eslint in the name unless they are explicitly installed.
ref: pnpm/pnpm#8378

Because of this, @nuxt/eslint-config and eslint-flat-config-utils are no longer hoisted,
TypeScript cannot find the type definition, and the types of exports in .nuxt/eslint.config.mjs is treated as any.

Additional context

There are two possible measures to address this.
One is to include @nuxt/eslint-config and eslint-flat-config-utils in the required peer dependencies
so that they are explicitly installed when we run nuxi module add eslint.
(This is because nuxi automatically and explicitly installs required peer dependencies when adding a module.)

The second is to update the documentation and add caution with pnpm v10.

It would be good to do both, and I am willing to do it!

Logs

[danielroe]

you can also add them typescript.hoist nuxt options within the module, which should resolve

[sushichan044]

Sounds great that way, how about the module automatically edit typescript.hoist options?

There are two possible ways:

• always edit the settings
• only edit when pnpm over v10 is used

I think the later way is better.

[danielroe]

I think the module should always add them into the options (not by editing the config but by pushing them into the array)

[sushichan044]

Sorry, yes, that would be a more consistent behavior.

In reading the nuxt initialization process, I also found that typescript.hoist is processed before the module is loaded,
so adding typescript.hoist from module currently does not affect final paths in .nuxt/tsconfig.json.

Therefore, I don't think I can add the hoist from the module right away,
so I plan to add documentation or a console warning as a workaround
that users can add the typescript.hoist and resolve this issue themselves.

[sushichan044]

Also, since typescript.hoist does not support subpath,
imports in .nuxt/eslint.config.d.mts must be changed from @nuxt/eslint-config/flat to @nuxt/eslint-config.

- import { defineFlatConfigs } from "@nuxt/eslint-config/flat"
- import type { NuxtESLintConfigOptionsResolved } from "@nuxt/eslint-config/flat"
+ import { defineFlatConfigs } from "@nuxt/eslint-config"
+ import type { NuxtESLintConfigOptionsResolved } from "@nuxt/eslint-config"

This should not be a problem since exports from . and /flat is the same since v1.0 release.