Mode Support for Vite Deployments

[hkropp]

I have a vite app and would like firebase to support different modes during deployment.

Vite uses modes to pick up environment variables like so:

.env                # loaded in all cases
.env.local          # loaded in all cases, ignored by git
.env.[mode]         # only loaded in specified mode
.env.[mode].local   # only loaded in specified mode, ignored by git

From the vite documentation: https://vite.dev/guide/env-and-mode#env-files

In my case, the Firebase API key among other variables is defined inside the .env.[mode] configuration files.

So that, if I deploy to staging or production, it would be great to be able to define the mode during firebase deploy --only hosting such that the right configuration is picked up.

Currently, one gets the following warning if changing the build command in package.json:

WARNING: Your package.json contains a custom build that is being ignored. Only the Vite default build script (e.g, "vite build") is respected. If you have a more advanced build process you should build a custom integration https://firebase.google.com/docs/hosting/express

It would be great if the vite modes and the defined environments in .firebaserc would be the same. So, in case of using firebase use ENV, which would also be the selected build mode for vite.
This behavior would be similar to the current behavior using the Firebase emulator, where the development mode is being used.

[leoortizz]

Hey @hkropp, thanks for reporting your issue. In this case you should be able to use a parameterized configuration to achieve your goal. Please take a look at this comment: #7207 (comment) which is related to a similar issue.

In this case you should modify your .env files to be named with the related project ids.

Let me know if that solves your main issue.

[google-oss-bot]

Hey @hkropp. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 3 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@hkropp if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.