ERROR (node:52837) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated

[pochat]

Environment

• Operating System: Darwin
• Node Version: v22.0.0
• Nuxt Version: 3.11.2
• CLI Version: 3.11.1
• Nitro Version: 2.9.6
• Package Manager: npm@10.6.0
• Builder: -
• User Config: devtools
• Runtime Modules: -
• Build Modules: -

Reproduction

-Install latest node
-Install latest nuxt
-npm run dev

Describe the bug

When upgrading to the latest node and the lastest nuxt version, the following error repeatedly appears in the console:
ERROR (node:52865) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated

The error is present at every npm run dev, and npm run build.

Additional context

No response

Logs

No response

[Infectious-Smile]

+1

[xiao-xiaozi]

use node version v19.2.0 can clear this error info

[RobinTail]

Odd versions of Node are not for production use, @xiao-xiaozi .
Use 20.x instead of 19, it's LTS now, and there should not be that deprecation warning.
https://github.com/nodejs/Release

[RobinTail]

ERROR (node:52865) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated

Why deprecation warning causes the error in nuxt?
Is there some configuration for that, @pochat ?

[ExEr7um]

ERROR (node:52865) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated

Why deprecation warning causes the error in nuxt?

Is there some configuration for that, @pochat ?

I don't think it causes any errors, just a simple warning.

[manniL]

For now, this is just a warning and can be ignored. ☺️

[danielroe]

This is an upstream issue (wooorm/import-meta-resolve#27) which is resolved in v4.1.0 of import-meta-resolve, but because nuxi inlines mlly, and mlly inline import-meta-resolve, it may take a little while for the fix to percolate downward into Nuxt.

cc: @pi0

[pi0]

wroking on mlly release expect it shortly :)

[igalklebanov]

@pi0 thank you! 💪

can we get a bump @ https://github.com/unjs/pkg-types ? still uses 1.6.1.

[manniL]

@pi0 thank you! 💪

can we get a bump @ unjs/pkg-types ? still uses 1.6.1.

refreshing the lockfile should be enough as it uses the ^1.6.1 constraint