-
Notifications
You must be signed in to change notification settings - Fork 950
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
is:npm hidden command is broken due to invalid config arguments (duplicate config) #6132
Comments
Actually, this seems a bit more severe as I'm also seeing the same error when running |
Is there a temporary workaround to this issue? Should I downgrade |
I've downgraded to 12.4.3 which doesn't have this bug. I also reproduced this on mac os in the mean time. My function deploys were failing with 12.4.4 because of this too. |
Any updates on this maybe? I'm stuck on 12.4.3 because my functions do not deploy with the the firepit version. |
I was attempting a PR to fix this, but it seems like bumping the @cookii-king The only workaround so far, if you want to use the standalone version of the firebase cli, is to stick to version 12.4.3 https://firebase.tools/ has instructions on how to get a specific version. The version installed through npm doesn't have this issue (I think, I hope 😅 ) |
Digging a bit deeper, there are errors when running the --edit-- I looked further into this, and the repackaged npm is indeed broken and throws an exception that is normally not shown. Tried some things to fix that packaging but I nothing that is working yet. I guess the short term solution would be to revert the npm dependency bump which would unbreak standalone versions of |
@hvisser Thanks for all the research into this, I'm looking into a fix now (hopefully without going all the way back to npm 6.x). Apologies for the delay on this - I had deprioritized it in my head since |
Thanks @joehan I didn't realise that either when I filed the issue initially, so I completely understand. |
I had the same problem today. Installing via "curl -sL https://firebase.tools | bash" we apparently still get a bad version... |
@Masterxilo There has not been a new version released since we fixed this bug, so that is expected. This should be resolved in the next version |
anyone fix this issue? |
Receiving this issue as well
|
This worked for me too. |
getting this with node --version && firebase --version v21.5.0 |
Hey @eszabo12 - this issue was fixed in 12.6.0. Please update to a more recent version of firebase-tools. |
I ran and am now getting this:
so it only runs with "sudo" prepended. Now am no longer getting the dual config error but instead this |
@eszabo12 Since that's a different error, could you open a new issue and include the |
I'm using the (hidden) is:npm function to check the latest available version of firebase-tools in my Github action.
I understand that this might be a bit on the edge of supported, however the
is:npm
function infirepit
seems broken at the moment, which is probably not intended :)[REQUIRED] Environment info
firebase-tools:
firebase-tools standalone 12.4.4
Platform:
ubuntu, did not test on other platforms, but could be equally affected.
[REQUIRED] Test case
run
firebase is:npm
[REQUIRED] Steps to reproduce
run
firebase is:npm
[REQUIRED] Expected behavior
Calls the embedded npm
[REQUIRED] Actual behavior
Returns an error similar to
The root cause seems to be that the same
npmrc
is passed tonpm
here https://github.com/firebase/firebase-tools/blob/master/standalone/firepit.js#L186 which apparently is no longer allowed.The text was updated successfully, but these errors were encountered: