-
Notifications
You must be signed in to change notification settings - Fork 198
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
Deploying Functions That Use Private NPM Package #178
Comments
So normally this should work with a
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
I'm trying to navigate deploying firebase functions that require the use of a private NPM package. So far, it's easy enough to authorize and install the private package and other dependencies, however, when I reach the last step in the job (i.e. using
firebase-action
to deploy the functions) the logs show that the step fails at the very end after the action seemingly attempts to runyarn install
AGAIN on its own and hits an authorization wall when trying to access/download the aforementioned private package. Not only does it seem redundant that the action attempts to install the dependencies for a second time, but it clearly also doesn't have access to the authorization token I provided in the 'setup node' step. I've tried a couple of workarounds including building an.npmrc
file to hold all of the package authorization/registry information as it does for me locally, but unfortunately I run into the same issue.The way I see it, there's a number of assumptions that could be made about what may be happening here. I'm certain I'm missing something though, so I'd really appreciate if someone could lend some insight...
Possible Assumptions:
firebase-action
isn't able to access the installed dependenciesfirebase-action
demands (for whatever reason) that the dependencies be re-installed but fails to reference/use authorization config/info for private packagesfirebase-action
is working fine, and thus a separate issue exists (i.e. a problem with one of the previous steps or a failure on my part to include a missing but necessary step).yml
FileScreenshots of Logs (w/Errors)
The text was updated successfully, but these errors were encountered: