Extension v0.2.3 fails to install - Node.js 22 not supported on Cloud Functions Gen 1

[moritztomasi]

Description:

The Stream Chat Authentication extension v0.2.3 fails to install due to specifying Node.js 22 runtime for Generation 1 Cloud Functions. According to Google's documentation and error messages, Gen 1 functions only support up to Node.js 20.

Steps to Reproduce:

• Attempt to install "Authenticate with Stream Chat" extension v0.2.3
• Installation fails with runtime validation errors

Expected Behavior:

The extension should install successfully.

Actual Behavior:

Installation fails with the following error for all functions:

Runtime "nodejs22" is not supported on GCF Gen1

Root Cause:

The extension.yaml file specifies nodejs22 runtime while using Generation 1 Cloud Functions, which is not a supported combination according to Google Cloud Functions documentation.

Suggested Fix:

Either:

• Downgrade to Node.js 20 or 18 runtime for compatibility with Gen 1 functions
• Migrate to Generation 2 Cloud Functions to use Node.js 22

[DaemonLoki]

Hey @moritztomasi,

sorry for getting back to you so late. We've released a new version of the extensions (v0.2.4) that uses the node 18 runtime throughout. We were able to reproduce this issue, but interestingly only in newly created Firebase projects. For some reason it kept working for older Firebase projects. Haven't heard any ideas from the team why that might be happening.

Upgrading to Gen2 cloud functions is not possible due to auth triggers not being available there, yet.

Let me know if the new versions solve the issue you were facing, and again - sorry for the late reply!

Best,
Stefan

[Purus]

This issue is still open in my older project with v0.2.4. I am unable to install the extension.

Failed to create 1st Gen function projects/platoniq/locations/us-central1/functions/ext-auth-activity-feeds-getStreamUserToken: runtime: Runtime validation errors: [error_code: \t DEPLOYS_NOT_ALLOWED\nmessage: \"Runtime nodejs18 is decommissioned and no longer allowed. Please use the latest Node.js runtime for Cloud Functions

[debjeetdebnath]

having same issue

[DaemonLoki]

I will take a look today at why this is happening.

Can you please report which action you're encountering this with and what setup you're using, @debjeetdebnath ?