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

Build 9.16.1 broke firebase deploy command #3664

Closed
ljle opened this issue Aug 11, 2021 · 5 comments
Closed

Build 9.16.1 broke firebase deploy command #3664

ljle opened this issue Aug 11, 2021 · 5 comments
Assignees

Comments

@ljle
Copy link

ljle commented Aug 11, 2021

[REQUIRED] Environment info

firebase-tools: 9.16.1

Platform: Windows through WSL with Arch Linux

[REQUIRED] Test case

There's no minimal test case as the bug is related to the deploy function.

[REQUIRED] Steps to reproduce

  • Deploy any cloud function.

[REQUIRED] Expected behavior

  • The function(s) are deployed and a successfull deployment message appears.

[REQUIRED] Actual behavior

  • Deployment "seems" to go through but at the end of the process an error is printed out. This happens both on CI or by issuing the command manually from the CLI.
    image
@JarrydMartin
Copy link

I am having the same issue.

When running firebase deploy with the debug flag I get the following error...

[2021-08-11T22:00:03.195Z] TypeError: track_1.default is not a function
    at release (/Users/jarryd/.nvm/versions/node/v14.17.3/lib/node_modules/firebase-tools/lib/deploy/functions/release.js:98:20)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

@bkendall
Copy link
Contributor

Looks like it. Taking a look...

@nternouski
Copy link

Same here

@taeold
Copy link
Contributor

taeold commented Aug 11, 2021

We are making a hotfix to address this.

In the meantime, please revert your Firebase CLI to the previously working version:

$ npm i -g firebase-tools@9.16.0

@bkendall bkendall self-assigned this Aug 11, 2021
@bkendall
Copy link
Contributor

Should be fixed in 9.16.2 now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants