DEP0155 Deprecation Warning with @iconify/utils

[Salunas]

DEP0155 Deprecation Warning with @iconify/utils in @nuxt/icon
Description
When building my Nuxt.js project, I encounter a DEP0155 deprecation warning related to @iconify/utils. The warning indicates the use of a deprecated trailing slash pattern mapping (./) in the exports field of the package.json file for @iconify/utils. This issue persists even after updating to the latest versions of @nuxt/icon and @iconify-json/tabler.
Steps to Reproduce

Create a Nuxt.js project with the following dependencies in package.json:"dependencies": {
"@nuxt/icon": "^1.13.0",
"@iconify-json/tabler": "^1.2.18",
"nuxt": "^3.17.4",
"vue": "^3.5.16",
"vue-router": "^4.5.1"
}

Configure @nuxt/icon in nuxt.config.ts:import tailwindcss from "@tailwindcss/vite";

export default defineNuxtConfig({
compatibilityDate: '2025-05-15',
devtools: { enabled: true },
css: ['~/assets/css/main.css'],
modules: ['@nuxt/icon'],
icon: {
mode: 'css',
cssLayer: 'base',
serverBundle: {
collections: ['tabler']
}
},
vite: {
plugins: [tailwindcss()],
build: {
sourcemap: false
},
css: {
devSourcemap: true
}
}
});

Run the build command:npm run build

Observe the following warning in the build output:(node:26620) [DEP0155] DeprecationWarning: Use of deprecated trailing slash pattern mapping "./" in the "exports" field module resolution of the package at D:\Projects\www\node_modules@iconify\utils\package.json imported from D:\Projects\www\node_modules@nuxt\icon\dist\runtime\server\api.js.

Expected Behavior
The build process should complete without any DEP0155 deprecation warnings related to @iconify/utils.
Actual Behavior
The build process completes successfully, but the DEP0155 deprecation warning is displayed, indicating an issue with the exports field in the @iconify/utils package.
Environment

Node.js Version: v22.16.0
Nuxt Version: 3.17.4
@nuxt/icon Version: 1.13.0
@iconify-json/tabler Version: 1.2.18
Operating System: Windows (PowerShell)
Other Relevant Dependencies:
vue: ^3.5.16
vue-router: ^4.5.1
@tailwindcss/vite: ^4.1.8
tailwindcss: ^4.1.8

Additional Context

The warning does not seem to affect the functionality of the application, as icons (e.g., tabler:star) render correctly.
I have tried updating @nuxt/icon and @iconify-json/tabler to the latest versions using npm install @nuxt/icon@latest @iconify-json/tabler@latest, but the warning persists.
A similar DEP0155 warning is also observed for @vue/shared, but this issue focuses on @iconify/utils.
I attempted to suppress the warning using NODE_OPTIONS=--no-deprecation with cross-env, which works but only masks the issue.

Suggested Fix
It appears that the @iconify/utils package uses a deprecated exports field format in its package.json. Updating the exports field to avoid the trailing slash pattern (./) could resolve this issue. Alternatively, if this is an upstream issue in @iconify/utils, please advise on any workarounds or planned updates.
Related Issues

Similar issue reported for @iconify/vue: nuxt/icon#140
Build size concerns with @nuxt/icon: nuxt/icon#188

[cyberalien]

Issue is incorrect as well as "suggested fix".

If you look at package, there is no ./ export. Deprecation warning is wrong.

Considering that it is happening only on Windows and cannot be reproduced on other operating systems or even when using WSL, this is a bug in Node for Windows. My guess is some incorrect internal path mapping when dealing with \ in Windows paths.

[Salunas]

Hi, thanks for the clarification — that makes sense now.

You're right, I double-checked the @iconify/utils/package.json (v2.3.0), and there's no ./ export entry. The only relevant entry is "./": "./", which is perfectly valid. So this indeed seems to be a false positive warning, likely triggered by Node.js on Windows misinterpreting dynamic export patterns.

For context, I'm using:

Node.js v22.16.0

Windows 10, PowerShell terminal

Even though it’s benign, the DEP0155 warning still appears on every build, even on freshly scaffolded Nuxt projects. That can lead to:

Confusion for developers (especially those unfamiliar with Node internals),

False assumptions about broken or outdated dependencies,

Unnecessary issue reports.

Suggestion
Perhaps Nuxt could:

Mention this in the documentation,

Or even show a short, friendly message in the build log (when on Windows) clarifying that DEP0155 is known, harmless, and does not affect functionality.

This would go a long way in:

Reassuring developers that their setup is working as expected,

Keeping the build output clean and trustworthy,

Reducing noise in issue trackers.

Thanks again for the quick and helpful reply — much appreciated!

[cyberalien]

I think a clean bug report for Node would be the best solution. Then Node team can fix that bug and until then issues can be redirected to that bug report.

I cannot make one myself because I don't use Windows and cannot reproduce that issue.

[Salunas]

Hi, thanks again for the quick response.

Just wanted to let you know that I’ve created a bug report for the Node.js team regarding the DEP0155 warning on Windows:

🔗 nodejs/node#58650

Hopefully this helps clarify the root cause and reduce confusion for other Windows users.

Thanks again for maintaining these tools!