Firebase-tools: Cannot update firebase-tools past version 3.19.1

Created on 16 Aug 2018  Â·  7Comments  Â·  Source: firebase/firebase-tools

Version info

v3.19.1

Platform Information

Mac OS 10.13.6

Steps to reproduce

Stuck on version 3.19.1.

Expected behavior

When I run npm install -g firebase-tools I expect it to update.

Actual behavior

When I run firebase --version it still says 3.19.1

Most helpful comment

Had a similar problem, was on firebase-tools version 3.19.3 and couldn't get past. Tried uninstalling and the firebase command still worked, despite npm letting me know it was uninstalled. Even went as far as downloading the folders so that the command didn't work anymore. Installing firebase again didn't help, the command was still unavailable.

Seems all people have this problem are also using a Mac. Found a thread saying node versions downloaded with homebrew are kinda bugged. I uninstalled node and npm entirely. Downloaded it from the downloads page. Installed firebase globally again.

And then it worked.

TL;DR
uninstall and reinstall node from the downloads page. You may have installed node originally using homebrew and have a bugged version of node.

All 7 comments

What happens if you do:

npm i -g firebase-tools@latest

Also, when it is installing what version does it say is installing?

Best guess is you may have multiple global npm directories and you're not
installing into the correct one.

On Thu, Aug 16, 2018, 3:23 AM Jason Newman notifications@github.com wrote:

Version info

v3.19.1
Platform Information

Mac OS 10.13.6
Steps to reproduce

Stuck on version 3.19.1.
Expected behavior

When I run npm install -g firebase-tools I expect it to update.
Actual behavior

When I run firebase --version it still says 3.19.1

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-tools/issues/873, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAAD_nXubOFW4BVE72Wfyjv5QB280auwks5uRR3ggaJpZM4V_VLW
.

If I do @latest it appears that it is installing and it gives me this:

/usr/local/Cellar/node/8.7.0/bin/firebase -> /usr/local/Cellar/node/8.7.0/lib/node_modules/firebase-tools/bin/firebase
/usr/local/Cellar/node/8.7.0/lib
└── [email protected]
version 4.1.1

but when I use the command firebase --version it still says 3.19.1

When I get off of work I will investigate whether I have more than one directory.

Thank you for your suggestions.

I am only finding one firebase-tools folder on my computer. It is in the functions folder of my firebase project. I am using firestore, functions and hosting for my project.

What do you get when you run

which firebase
which node
which npm

On Thu, Aug 16, 2018, 1:01 PM Jason Newman notifications@github.com wrote:

I am only finding one firebase-tools folder on my computer. It is in the
functions folder of my firebase project. I am using firestore, functions
and hosting for my project.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-tools/issues/873#issuecomment-413615299,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAD_rBvUBk-qOqfCrIhdvehSCe16lwAks5uRaVtgaJpZM4V_VLW
.

/usr/local/bin/firebase
/usr/local/bin/node
/usr/local/bin/npm

Thank you for your help with getting the tools updated. Now to figure out why hosting cannot find my css and image files anymore.

Had a similar problem, was on firebase-tools version 3.19.3 and couldn't get past. Tried uninstalling and the firebase command still worked, despite npm letting me know it was uninstalled. Even went as far as downloading the folders so that the command didn't work anymore. Installing firebase again didn't help, the command was still unavailable.

Seems all people have this problem are also using a Mac. Found a thread saying node versions downloaded with homebrew are kinda bugged. I uninstalled node and npm entirely. Downloaded it from the downloads page. Installed firebase globally again.

And then it worked.

TL;DR
uninstall and reinstall node from the downloads page. You may have installed node originally using homebrew and have a bugged version of node.

Was this page helpful?
0 / 5 - 0 ratings