Cannot read properties of undefined (reading 'provider') - nuxt apps not starting anymore

[mklueh]

Environment

---

• Operating System: Windows_NT
• Node Version: v22.9.0
• Nuxt Version: 3.13.2
• CLI Version: 3.14.0
• Nitro Version: 2.9.7
• Package Manager: [email protected]
• Builder: -
• User Config: -
• Runtime Modules: -
• Build Modules: -

---

Reproduction

I haven't changed the code itself, but uninstalled some dependencies and updated everything to latest.

Modules used:

  modules: [
    "@unocss/nuxt",
    "@nuxt/content",
    "@vueuse/nuxt",
    "@nuxt/fonts",
    // @ts-ignore
    "@nuxtjs/seo",
    "@nuxt/icon",
    "nuxt-umami"
  ],

Dependencies upgraded:

Transitive deps of "@nuxt/icon"

I've tried it with and without the icon config in nuxt.config.ts with no effect

Describe the bug

I`m suddenly getting this error after upgrading a few dependencies and the site is not loading anymore.

Additional context

No response

Logs

Cannot read properties of undefined (reading 'provider')
Stacktrace
setup
@nuxt/icon/dist/runtime/plugin.js:16:17
(anonymous)
./C:/Users/MyPC/Workspace/my-project/apps/my-app/virtual:nuxt:C:/Users/MyPC/Workspace/my-project/apps/my-app/.nuxt/plugins/server.mjs:77:89
Module.executeAsync
unctx/dist/index.mjs:111:19
setup
./C:/Users/MyPC/Workspace/my-project/apps/my-app/virtual:nuxt:C:/Users/MyPC/Workspace/my-project/apps/my-app/.nuxt/plugins/server.mjs:77:65
(anonymous)
nuxt/dist/app/nuxt.js:146:60
fn
nuxt/dist/app/nuxt.js:228:44
Object.callAsync
unctx/dist/index.mjs:68:55
(anonymous)
nuxt/dist/app/nuxt.js:231:56
Object.runWithContext
@vue/runtime-core/dist/runtime-core.cjs.js:3940:18
callWithNuxt
nuxt/dist/app/nuxt.js:231:24

Besides these logs from the devtools plugins I see nothing in the actual logs, even with debug and dev flag

[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 prioritize 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

[manniL]

Stacktrace points towards this plugin in @nuxt/icon.