You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue does not have all the information required by the template. Looks like you forgot to fill out some sections. Please update the issue with more information.
@yanqianglu If your pages use SSR you can rename your dotenv file to .env.<PROJECT-ID> instead of .env.<PROJECT-ALIAS> and you should be able to read the environment variables in that file. You can read more about it in the Parameterized configuration for Cloud Functions.
I have opened a PR (#7323) to handle the issue when using SSG in Next.js. But the idea is the same, we would read the values from the .env.<PROJECT-ID>.
[REQUIRED] Environment info
firebase-tools: 13.10.0
Platform: macOS
[REQUIRED] Test case
See "Steps to reproduce" below.
[REQUIRED] Steps to reproduce
[REQUIRED] Expected behavior
It should take the
.env.stg
file as part of the build.[REQUIRED] Actual behavior
It only takes
.env
file and ignored.env.stg
file. The.env.stg
is included as part of the functions deployment though.The text was updated successfully, but these errors were encountered: