Skip to content

EACCESS with npm install -g firebase-tools #25325

Answered by w9jds
anandchakru asked this question in Actions
Discussion options

You must be logged in to vote

This was actually caused by firebase-tools due to how docker works (It pulls and installs latest tool version each time it runs) it pulled a bad version, there are issues opened to fix it. However, I have pushed v1.4.0 which addresses the issue and uses a workaround to get it to work. If you are pointing to master, the build should just work now if you re-run it. Otherwise, point your action to the latest release and you should be good.

Note, it was reproducible with a local version of docker as well.

Replies: 5 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants