FR: allow import 'firebase/remote-config' for server side rendering

[hecateball]

[REQUIRED] Describe your environment

• Operating System version: (not related)
• Browser version: (not related)
• Firebase SDK version: 7.1.0
• Firebase Product: Remote Config

[REQUIRED] Describe the problem

Importing 'firebase/remote-config' where the Window object is undefined throws error, thus we have to avoid import 'firebase/remote-config' at server side rendering.

(Specifically, this is quite troublesome for universal web apps built with Nuxt.js. Since this issue
occurs when import files using 'firebase/remote-config', it cannot be used in any Vue components, or must use dynamic import and treat Promise somehow...)

It would be highly appreciated if firebase/remote-config run without caching on server side. At least, make it possible to import without the Window object.

Steps to reproduce:

1. import 'firebase/remote-config' in any javascript code.
2. run that code wherever the Window object is undefined.

Relevant Code:

https://github.com/firebase/firebase-js-sdk/blob/master/packages/remote-config/index.ts#L48-L51

[erikeldridge]

@hecateball Thx for the feedback!

Is the goal to fetch config server-side, or just build in the Node env? I ask because the former has product considerations, but the latter might be more straightforward.

If anyone else would benefit from the same, plz upvote using a reaction on the issue.

[hecateball]

@erikeldridge Sorry for the late reply...
My goal is to fetch config server-side (run the same code both server-side and client-side).

Currently, I'm bypassing fetch config server-side (using default config) so the application generates different page for the same URL depending on which environment that page is rendered (server-side/client-side).

I'd like to generate same page both in server-side and in client-side by single code.

[erikeldridge]

Thx for clarifying!

Unfortunately, fetching server-side isn't a quick change :( For example, the percent condition requires a stable identifier, the location condition considers the caller's IP address, etc. Although it's still JS, it's almost another platform.

I'll leave this issue open so folks can up-vote, which helps us prioritize.

[hecateball]

@erikeldridge
Is it possible to change when an error occurs?
It would be good enough if we could import remote-config module server-side without any errors. Instead, fetching config server-side may cause error but we can handle it.

Our biggest problem is that we have to use dynamic import everywhere we use remote-config module and it makes application code messy...

[Asherlc]

Any update on this? This is currently a blocker for us using remote config at all

[liveHarshit]

same @Asherlc

[stnmonroe]

Thx for clarifying!

Unfortunately, fetching server-side isn't a quick change :( For example, the percent condition requires a stable identifier, the location condition considers the caller's IP address, etc. Although it's still JS, it's almost another platform.

I'll leave this issue open so folks can up-vote, which helps us prioritize.

Could the stable identifier be stored in a cookie so it can be used server side and passed into the remote config function?