onInit does not support multiple invocations

[PhilipSkinner]

Related issues

None.

[REQUIRED] Version info

firebase-functions: 6.4.0

node:

v20.19.4

firebase-functions:

firebase-tools:

14.11.1

firebase-admin:

13.2.0

Test case

Firebase functions emulator entry point:

export * from '@my/apiOne';
export * from '@my/apiTwo';

@my/apiOne entry point:

import {
    onInit
} from 'firebase-functions/v2/core';
import { 
    onRequest 
} from 'firebase-functions/v2/https';

let value = null;
onInit(async () => {
    value = await someLongProcess();
});

export const apiOne = onRequest({ 
    cors: true
}, async (req, res) => {    
    return value.handler(req, res);
});

@my/apiTwo entry point:

import {
    onInit
} from 'firebase-functions/v2/core';
import { 
    onRequest 
} from 'firebase-functions/v2/https';

let value = null;
onInit(async () => {
    value = await someLongProcess();
});

export const apiTwo = onRequest({ 
    cors: true
}, async (req, res) => {    
    return value.handler(req, res);
});

Steps to reproduce

Break down code to contain functions separately yet have the emulator execute them singularly.

Expected behavior

onInit allows multiple calls where each async function passed is executed (await Promise.all(...);).

This is required to break firebase code down into separate functions when running the emulator locally.

Actual behavior

Calling onInit more than once only calls the last function passed to it:

{"severity":"WARNING","message":"Setting onInit callback more than once. Only the most recent callback will be called"}

Were you able to successfully deploy your functions?

Deploy yes, run locally no. onInit functionality breaks using the emulators.

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[CorieW]

Hi @PhilipSkinner

Thanks for reporting this issue! We’ve received it and are reviewing it. We’ll provide updates as soon as possible.

[CorieW]

An alternative may be restructuring your code to something like the following:

index.js:

import {
    onInit
} from 'firebase-functions/v2/core';
import {
    onInit as onInitApiOne
} from '@my/apiOne';
import {
    onInit as onInitApiTwo
} from '@my/apiTwo';

export * from '@my/apiOne';
export * from '@my/apiTwo';

onInit(async () => {
    // TODO: Add logic
    await onInitApiOne();
    await onInitApiTwo();
});

@my/apiOne:

import { 
    onRequest 
} from 'firebase-functions/v2/https';

let value = null;
export async function onInit() {
    value = await someLongProcess();
}

export const apiOne = onRequest({ 
    cors: true
}, async (req, res) => {    
    return value.handler(req, res);
});

@my/apiTwo:

import { 
    onRequest 
} from 'firebase-functions/v2/https';

let value = null;
export async function onInit() {
    value = await someLongProcess();
}

export const apiTwo = onRequest({ 
    cors: true
}, async (req, res) => {    
    return value.handler(req, res);
});

@PhilipSkinner thoughts on this approach?

[inlined]

Additional Q: I notice that your samples have init functions that are specific to any given function. Since each function is deployed to a different container, would it be more desirable (i.e. more performant/reliable) that the existing tool is for global/universial initialization and a new tool exists to run initialization code only when a given function is active in a container? E.g.

@my/apiOne

import { 
    onRequest 
} from 'firebase-functions/v2/https';

export const apiOne = onRequest({ 
    cors: true
    onInit: async () => (value = await someLongProcess()),
}, async (req, res) => {    
    return value.handler(req, res);
});