HOSTING: Express.js / custom not an option in CLI

[conshus]

Hi all. Super excited about the different Web Frameworks integration. My ultimate goal is to get an Astro SSR application up and running. In the past, to get something running with Sapper, there were a bunch of steps so I'm happy to see this happening.

First, I tried with an Astro SSR Node (middleware / Express) project. After messing around, I was able to deploy successfully, but it seems like the files are "hosted" (I can go directly to them in the browser), but are not "served" (site just shows Firebase "Page Not Found").

Decided to take a step back and try a basic Express app (from Stackblitz).

Following the steps in the documentation and GitHub repo, it says that I should see Express.js / custom as an option when initializing hosting. I didn't for either projects.

Here's a screenshot:

Here's what I'm using:
Firebase CLI version: 11.19.0
Chromebook with Debian GNU/Linux 11 (bullseye)

Further info, for the Astro project, I was able to get it to recognize it as an Express app, by making the hosting.source in firebase.json ".":
{ "hosting": { "source": "." } }
like the GitHub repo says and not like:
{ "hosting": { "source": "./path-to-your-express-directory", } }
that the documentation stated.

Any insight is greatly appreciated.
Thanks.

[gustavopch]

It doesn't appear because of this condition if (init) choices.push({ name, value });.

https://github.com/firebase/firebase-tools/blob/56fb8a34201ab903f92178f696bc3b28acfb79bb/src/init/features/hosting/index.ts#LL97C12-L97C12

I removed the condition in my local installation at node_modules/firebase-tools and it worked.