Functions Emulator error when using SEA preview build

[aalej]

[REQUIRED] Environment info

firebase-tools: 15.26.0 (SEA preview build)

Platform: macOS

[REQUIRED] Test case

[REQUIRED] Steps to reproduce

1. Run firebase init functions --project demo-project

✔ What language would you like to use to write Cloud Functions? JavaScript
✔ Do you want to use ESLint to catch probable bugs and enforce style? No
✔  Wrote functions/package.json
✔  Wrote functions/index.js
✔  Wrote functions/.gitignore
✔ Do you want to install dependencies with npm now? Yes

2. Update functions/index.js

const { onRequest } = require("firebase-functions/https");
const logger = require("firebase-functions/logger");

exports.helloWorld = onRequest((request, response) => {
    logger.info("Hello logs!", { structuredData: true });
    response.send("Hello from Firebase!");
});

3. Run firebase emulators:start --project demo-project
4. Open http://127.0.0.1:5001/demo-project/us-central1/helloWorld on a browser
   • This gets stuck

[REQUIRED] Expected behavior

There shouldn't be any errors when invoking functions on the Functions Emulator

[REQUIRED] Actual behavior

Functions Emulator shows these errors

>  Error: /Users/USER/.cache/firebase/tools/lib/node_modules/firebase-tools/lib/emulator/functionsEmulatorRuntime is not a Firebase command
⬢  functions: Failed to handle request for function us-central1-helloWorld
⬢  functions: Failed to start functions in /Users/USER/Desktop/firebase-tools/node-sea-test/func-emulator/functions: Failed to load function.

[joehan]

Thanks for reporting this!

Root Cause

When the Functions Emulator launches a worker process to handle function requests, it spawns functionsEmulatorRuntime (without the .js extension). In the standalone SEA binary, firepit.js's child-script detector expected exact file existence on disk (functionsEmulatorRuntime) rather than resolving .js/.cjs/.mjs extensions. Because functionsEmulatorRuntime without .js didn't exist directly on disk, the standalone binary treated it as a top-level CLI command and threw:
Error: .../functionsEmulatorRuntime is not a Firebase command.

Fix

1. Updated standalone/firepit.js to automatically resolve extensionless JavaScript script files (.js, .cjs, .mjs, and via require.resolve()) when invoked by child processes.
2. Updated src/emulator/functionsEmulator.ts to explicitly specify functionsEmulatorRuntime.js.
3. Added automated e2e test assertion for extensionless script resolution.

This has been released in pre-release v15.26.0-sea.preview.5.

[aalej]

Not sure if it's just me but I can't seem to run any commands using the v15.26.0-sea.preview.5 version.

1. Run curl -sL https://fir-tools-builds-staging.web.app | version=v15.26.0-sea.preview.5 upgrade=true bash
2. Run firebase --version
   • Outputs nothing

$ curl -sL https://fir-tools-builds-staging.web.app | version=v15.26.0-sea.preview.5 upgrade=true bash
-- Checking for existing firebase-tools...
-- Checking your machine type...
-- Downloading binary from https://firebase.tools/bin/macos-arm64/v15.26.0-sea.preview.5
######################################################################## 100.0%##O#-#                                                                         
-- Setting permissions on binary... /usr/local/bin/firebase
-- Checking your PATH variable...
-- firebase-tools@15.26.0 is now installed
-- All Done!
$ firebase --version

This is not reproducible on the old preview.4 version

$ curl -sL https://fir-tools-builds-staging.web.app | version=v15.26.0-sea.preview.4 upgrade=true bash
-- Checking for existing firebase-tools...
-- Checking your machine type...
-- Downloading binary from https://firebase.tools/bin/macos-arm64/v15.26.0-sea.preview.4
######################################################################## 100.0%#=#=#                                                                          
-- Setting permissions on binary... /usr/local/bin/firebase
-- Checking your PATH variable...
-- firebase-tools@15.26.0 is now installed
-- All Done!
$ firebase --version
15.26.0

[joehan]

We investigated this together, and it turns out that the binary works until you try to run any commands in a directory that includes a firebase.json. Both Alej and I were able to repro