I am trying to (re)install Firebase, however, when I run sudo npm install -g firebase-tools the following error shows up:
I have no idea what is wrong, it used to work well a few month ago.
You try running
npm cache clean
and then trying to install again.
If the error is not lost try below
Have you tried installing homebridge with the --unsafe-perm option?
sudo npm install -g --unsafe-perm homebridge
If npm detects it is running as root it drops to a non-privileged user which then doesn't have permissions to write to /root/.node-gyp. The --unsafe-perm option stops it from changing user.
nvm doesn't have this problem when not using sudo because it stores everything under the current users' home directory.
Related
I am trying to access an SQLite database from Node-Red. Node-Red is unable to open the DB. My OS is Ubuntu 18.04.3.
My flow and SQLite node definitions are provided below. The inject and debug nodes only have default values. I am keeping it very simple since this is my first attempt at SQLite with Node-Red.
When I deploy my flow, I get the following error:
The db has read-write-execute privileges for all users. It is local on my machine and I am the only one using it.
Any idea what could be causing the issue ?
All right here is how I solved the issue.
I was also having problems opening .csv files. By looking at other similar posts it seemed to be a user privilege problem which could not be resolved, even by changing the file privileges with chmod.
I had installed all the node components using different mediums:
nodejs and npm from the command line
node-red from the Ubuntu Software Center
node-red-dashboard and node-red-node-sqlite from the node-red browser.
These different installation mediums might have caused privilege issues. So I uninstalled everything.
I then reinstalled everything from the command line. Node packages were installed globally (i.e. with "-g" attribute):
sudo apt install nodejs
sudo apt install npm
sudo npm install -g node-red
sudo npm install -g node-red-dashboard
sudo npm install -g node-red-node-sqlite
I then confirmed npm could see everything as global packages:
sudo npm list -g --depth 0
I now launch node-red in a shell:
node-red
Then by going to a browser and typing:
localhost:1880
the node-red browser loads, all dashboard and sqlite nodes are available and I am able to read sqlite & csv files.
*** Note regarding installing node-red sub-packages ***
Node-red sub-packages (node-red-dashboard, node-red-node-sqlite, ...) can be installed from npm or from the node-red browser.
However I noticed a few things:
a sub-package installed from the browser will not show up when typing npm list -g --depth 0.
a sub-package installed with sudo npm -g <sub-package> will show up with npm list -g --depth 0.
packages listed in the browser will not all show up with command npm list <package>.
So I decided to play it safe and install all my node-red sub-packages with npm list. First I search for my sub-package in the node-red browser palett list, I retrieve the sub-package name, then I install it from the shell using sudo npm -g <sub-package>.
Consistency solved the problem: installing everything from the shell as global packages.
Here's the entire error message....
Command 'ASK: Deploy the skill' resulted in an error (ASK CLI v1 is not functional. Command failed: C:\WINDOWS\system32\cmd.exe /q /s /c "ask init -l" error: unknown option '-l' )
Happens when I 'ASK deploy' or any ASK command. Anybody have any ideas what that means?
TIA!!
I figured it out and assuming you are a windows user, this may be your issue.
Before you install ASK-CLI on Windows, you must install the Node.js windows-build-tools package. Before you install windows-build-tools, make sure you have the version of Node.js that the package requires. If you have already installed ASK-CLI you need to uninstall it. Then install it again after you have installed windows-build-tools.
To install windows-build-tools, first open PowerShell with the Run as Administrator option, then type npm install -g --production windows-build-tools.
After I did this, I had to delete and recreate my ASK project, then my ASK deployments started working.
Reference: https://developer.amazon.com/en-US/docs/alexa/smapi/quick-start-alexa-skills-kit-command-line-interface.html
I have a step by step to setup a new environment:
npm install -g --production windows-build-tools
npm install -g ask-cli
ask configure
npm install -g lambda-local
Please assure that you are running the command as Administrator or using sudo on Linux.
I'm using Mac OS 10.15.2, Terminal 2.10.
I'm trying to install firebase tools to allow me to upload my experiment to firebase.
The following is what I used to do, which had been giving me success. But today, I'm using a new computer, and the installations were unsuccessful. I'm pasting the record in command line, as a screenshot, here for your reference
.
Thank you very much!
You are using the wrong package. You should be using "firebase-tools" instead of "firebase-cli". Be sure to read through the warnings and errors carefully.
Uninstall the old firebase-cli package:
sudo npm uninstall -g firebase-cli
Then install the correct firebase-tools package:
sudo npm install -g firebase-tools
Try running the command with sudo i.e use the command
sudo npm install -g firebase-tools
I cannot, as the title suggests, upgrade or in any way remove the current version of firebase off my system and I don't understand why. I installed it using the firebase commands prompted when you first start a project, something in line with npm install -g firebase-tools. After I've installed other packages to go along with it and I've upgraded the packages accordingly.
Now I want to remove the package I just do not understand how to do it. I've run
npm uninstall -g firebase-tools
npm uninstall -g firebase-admin
npm uninstall -g firebase-functions
npm uninstall -g firebase*
...and many other variations. After a while of trying I just figured I'll check what packages may still be left.
npm ls | grep firebase
Shows no firebase packages are still installed, however, running any firebase command will still work perfectly. Running firebase --version I get 3.15.4. I've also, just as a Hail Mary, tried running apt remove --purge firebase*
Further digging I figured that maybe the npm ls command was off, so I tried reinstalling all firebase packages. I ran it again and there they were, however* firebase was now at version 4.12.1. Running firebase --version still produce 3.15.4.
I'm really lost at this point. All help articles relating to uninstalling firebase leads to either how to delete projects or databases or to npm's how to uninstall a package website.
Sincerely.
You can't delete it, because you need to remove entire folder. This worked for me when I ran into the same problem:
which firebase
This locates the folder where firebase is (in Mac case it's /usr/local/bin/firebase) and then you do:
rm /usr/local/bin/firebase
Now do firebase -V and you'll get Command firebase not found. And now you can install back firebase with the real latest actual version:
npm i -g firebase-tools#latest
However, if you run firebase it will still give you Command firebase not found for what you can do this:
alias firebase="`npm config get prefix`/bin/firebase"
Worked for me with almost exactly the same problem.
Hope this helps you too!
i am windows user and trying to update firebase version using
npm install -g firebase-tools but when i run firebase --version
it shows the same version.
I also run npm uninstall firebase --save and check firebase --version it shows same.
what should i do to update my firebase version?
npm update -g firebase-tools
or
npm install -g firebase-tools#3.12.0 to install a specific version
And make sure to restart your terminal/IDE otherwise, it won't take effect.
Have you tried npm update -g firebase-tools? This worked for me.
These days if you're on an older version, and you check the version of firebase-tools, by running:
firebase -V
along with the version of firebase-tools that you're on, it also gives you a messages, something like this:
So you can basically run npm i -g firebase-tools to update the version of your firebase-tools installation to the latest version.
Hope this helps :)
For other like me stumbling in with a weird version mismatch:
When I did firebase -V in my terminal I would get a different version (5.1.1) than when I ran firebase through a npm run script (3.19.3)
The problem was that I had previously installed firebase locally into that project. In other words, I was getting the global version in the terminal, but npm was using the node_modules version
To confirm this, I added a simple test called test-foo to my package.json (firebase -V && which firebase) and ran it:
kuzyn(λ)matebox‡ npm run test-foo
kuzyn-project#1.1.0 test-foo /home/kuzyn/code/kuzyn-project/firebase
firebase -V && which firebase
3.19.3
/home/kuzyn/code/kuzyn-project/firebase/node_modules/.bin/firebase
Then I removed the (uneeded in my case) local firebase package from the package.json and from node_modules
Try the 2 steps bellow
1. yarn/npm cache clean
2. npm install -g firebase firebase-tools or yarn add -g firebase firebase-tools
in a new terminal, firebse --version
works for me
it works to me...
standalone binary: Download the new version, then replace it on your system
if you are using the standalone.Download the new version
In my case I was using an old node version (v10) and had to switch to a newer one (v12). After that I ran npm install -g firebase-tools again and it was updated to the latest version.
You can check the current node version by running node -v. And I use nvm to switch to a different node version.
That might happen in case you've installed the firebase-cli using a so called automatic install script.
Try to call curl -sL https://firebase.tools | upgrade=true bash as described in the official documentation