-
Notifications
You must be signed in to change notification settings - Fork 356
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
Unable to deploy to AWS EBS #105
Comments
Can you check if the |
How do I check the contents of node_modules folder in ebs? In my local node_modules folder I see the |
This should be fixed now: https://firebase.google.com/support/release-notes/admin/node#5.4.3 We no longer load Firestore/gRPC packages unless |
@hiranya911 I have to use firestore for my project, are there any workarounds? Also, when I take out any firestore call (it was easy as I was only using it in one place) I get
So I can't use it even if I don't call firestore |
@shadow1349 I switched from NPM to yarn on EB and it works great now. |
@rtkhanas I'm afraid I can't switch my whole company over to yarn |
@shadow1349 anyway the problems looks like NPM is installing some dependencies to a wrong folder on AWS. Maybe, not really related to firebase-admin-node, but more to NPM itself. |
Hello all, have this issue been resolved? I am getting it too. Any suggestions? |
I have this issue too, we we're running t2.micro with 512MB ram, but compiling GRPC module seems to only work with t2.medium (4GB ram). Why is this package installed when I'm just using firebase.messaging() ? |
appreciate you @albinekb , upgraded t2.mico => t2.medium and it worked. |
For any latecomers to this thread: I encountered this issue when deploying to Elastic Beanstalk. Installing
I was able to resolve temporarily by installing with |
@sthielen thank you. This worked perfectly for me |
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
npm install --save firebase-admin
and runeb-deploy
The deploy fails with:
Here is my package.json
The text was updated successfully, but these errors were encountered: