I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

Thanks for reporting this @chrisspiegl . I'll take a look.

@chrisspiegl I just found out that we have a typo in one of our package.json files. I've posted #8331 to fix the typo, but I'm not certain if that's the root cause of the error you're seeing. Could you manually fix this in your project and let me know if it helps?

@ehsannas thank you for looking into this. I tried looking how I may be able to check this typo but did not find a way to do this. It appears I would have to completely build the SDK myself, which I currently do not have the time to do / test / figure out. Sorry 😢.

I haven't been able to reproduce the error unfortunately.

My package.json is:

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "dependencies": {
    "firebase": "10.12.0",
    "firebase-admin": "12.1.1",
    "nuxt": "^3.12.2",
    "nuxt-vuefire": "1.0.2"
  }
}

Could you point me to a minimal reproduction repository?

@ehsannas Is the #8331 released in a version?
Maybe I can check with that and see if the issue is still present.

It'll be released soon after #8345 lands

Hey @chrisspiegl. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

@ehsannas I looked into this again and tried to figure out if #8331 has been released. To me, it looks like it's not been released. Just updating here since the bot made that comment.

@ehsannas I looked into this again and tried to figure out if #8331 has been released. To me, it looks like it's not been released. Just updating here since the bot made that comment.

Hi @chrisspiegl, this change was released in 10.12.3, but I accidentally did not include this change in the release notes.

The change was added to the changelog in 52f8deb, and you can also see it listed in the changes in the GitHub release.

I'm sorry for any confusion- my bad!

I updated to version 10.12.4 in our code base and the errors from my initial issue are gone.

Thank you. This appears to be fixed.