Support .env files in web frameworks

[jamesdaniels]

Fixes #5247

[leoortizz]

LGTM! I deployed a Next.js app and the variables from .env were available in my APIs.

Do we also need to handle .envs based on NODE_ENV? Like .env.development .env.production .env.test?

[jamesdaniels]

Do we also need to handle .envs based on NODE_ENV? Like .env.development .env.production .env.test?

The glob copy should move anything that starts with .env. into the code-generated functions directory, so should work out of box ;)

[leoortizz]

Do we also need to handle .envs based on NODE_ENV? Like .env.development .env.production .env.test?

The glob copy should move anything that starts with .env. into the code-generated functions directory, so should work out of box ;)

I see. Was thinking about not deploying .env.test/.env.development to production

[codecov-commenter]

Codecov Report

Base: 56.19% // Head: 56.17% // Decreases project coverage by -0.02% ⚠️

Coverage data is based on head (883ff9c) compared to base (17de2ab).
Patch coverage: 16.66% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5501      +/-   ##
==========================================
- Coverage   56.19%   56.17%   -0.02%     
==========================================
  Files         317      317              
  Lines       21461    21470       +9     
  Branches     4381     4383       +2     
==========================================
+ Hits        12059    12060       +1     
- Misses       8342     8350       +8     
  Partials     1060     1060              

Impacted Files	Coverage Δ
src/frameworks/index.ts	15.05% <16.66%> (-0.14%)	⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.