Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bloom Blob Missing Specifier in firebase@10.12 #8319

Closed
chrisspiegl opened this issue Jun 15, 2024 · 11 comments
Closed

Bloom Blob Missing Specifier in firebase@10.12 #8319

chrisspiegl opened this issue Jun 15, 2024 · 11 comments
Assignees

Comments

@chrisspiegl
Copy link

Operating System

macOS 14.5

Browser Version

irelevant

Firebase SDK Version

10.12.0

Firebase SDK Product:

Analytics, AppCheck, Auth, Firestore, Performance

Describe your project's tooling

Nuxt@3.12.1
nuxt-vuefire@1.0.2
firebase-admin@12.1.1

Describe the problem

I upgraded to the latest version of firebase with any of the versions above 10.12.0 and get the following errors when running my project:

⚙ [nuxt] warmup for @firebase/webchannel-wrapper/bloom-blob failed with: Missing "./bloom-blob" specifier in "@firebase/webchannel-wrapper" package
⚙ [warmup] tracking dependencies for @firebase/webchannel-wrapper/bloom-blob failed with: Missing "./bloom-blob" specifier in "@firebase/webchannel-wrapper" package

These do not happen with version firebase@10.11 (tested 10.11.1) and have not happened before.
When downgrading to firebase@10.11 the issues are no longer present.

I hope this can be fixed and upgraded so we can safely upgrade to v10.12.

Steps and code to reproduce issue

Install the described dependencies. Especially firebase@10.12.
Then run the build and the issue comes up in development (after the browser urls are shown).

@chrisspiegl chrisspiegl added new A new issue that hasn't be categoirzed as question, bug or feature request question labels Jun 15, 2024
@google-oss-bot
Copy link
Contributor

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

@chrisspiegl chrisspiegl changed the title Bloom Blob Jun 15, 2024
@jbalidiong jbalidiong added api: core needs-attention and removed needs-triage new A new issue that hasn't be categoirzed as question, bug or feature request labels Jun 17, 2024
@ehsannas
Copy link
Contributor

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

@ehsannas ehsannas self-assigned this Jun 21, 2024
@ehsannas
Copy link
Contributor

@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?

@chrisspiegl
Copy link
Author

@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 😢.

@ehsannas
Copy link
Contributor

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

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?

@chrisspiegl
Copy link
Author

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

@ehsannas
Copy link
Contributor

ehsannas commented Jul 2, 2024

It'll be released soon after #8345 lands

@google-oss-bot
Copy link
Contributor

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!

@chrisspiegl
Copy link
Author

@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.

@dlarocque
Copy link
Contributor

dlarocque commented Jul 9, 2024

@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!

@chrisspiegl
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
6 participants