James Daniels

Thanks for the fix, I'll look at merging this in for a patch release ASAP

Thanks for updating. Shout out to @davideast who did the vite integration

Vite has been integrated with the latest generation of the tooling, frameworks that use Vite should "just work" for non-SSR ATM. We'll be looking into deeper integrations.

Sorry about that, we missed a TODO while we were moving the code into firebase-tools. We'll get this addressed shortly.

Working on this and the Next 13 fixes here https://github.com/firebase/firebase-tools/pull/5175

Fixed in the latest CLI release

Interesting, probably worth us copying over any npmrc into the code generated Cloud Function

We're looking into other frameworks but have no timelines to share. In the meantime we offer two DIY integrations: Vite and Express/custom. Vite should "just work" out of box (non-SSR...

Here's the docs on the custom integration https://firebase.google.com/docs/hosting/express

There's also an environment variable that is respected ```yaml - uses: FirebaseExtended/action-hosting-deploy@v0 with: # ... env: FIREBASE_CLI_EXPERIMENTS: webframeworks ```