Firebase client — fails import with Code Error could not compute configurable props

Help
1

Hi team!

I’m trying to connect as a client to a Firebase of the external app, and as soon as I add

import firebase from "firebase";

to my node.js step, it starts to fail tests with an error: Code Error could not compute configurable props

image

Is it expected?

i know, there is Firebase Admin SDK, but I don’t think it suits me well, because I don’ own the database. My final goal is to be able to access Settle UP Database as my own user, to dump my own transactions.

Thanks in advance.

2

Hi @okdimok,

First off, welcome to Pipedream! Happy to have you.

Per the firebase documentation as the image below, the library only supports Client platform such as the Web, mobile Web (e.g. React Native, Ionic), Node.js desktop (e.g. Electron), or IoT devices running Node.js

image
image1920×1112 126 KB

As Pipedream runs your workflow in AWS Lambda, I don’t think this library will compatible with it. As in the document stated, you can use Firebase Admin Node.js SDK instead, or you can connect with the realtime database using REST API

3

Hi @vunguyenhung!

Citing from the same doc as your screenshot

This package supports web (browser), mobile-web, and server (Node.js) clients.

I read the fragment you quote with the emphasis on

If you are interested in using an SDK which grants you admin access, you should use the Firebase Admin Node.js SDK.

So I still think there is some compatibility issue between the legit server-side npm package and Pipedream. How can I further debug it myself? Should I look for the props js property exported somewhere in the package?

4

Hello @okdimok,

Pipedream executes your workflow in an AWS Lambda function, hence some libraries will not be compatible .e.g. puppeteer. I believe the package install some other dependencies that are not compatible with Node.js but NOT AWS Lambda.

How can I further debug it myself? Should I look for the props js property exported somewhere in the package?

I think this is Pipedream internals and you don’t have the control over it. The action you can do is you can submit a ticket for Pipedream here