fix(vite): load .env files into process.env in dev

[markdalgleish]

Fixes #7934

[changeset-bot]

🦋 Changeset detected

Latest commit: c6cfa88

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages

Name	Type
@remix-run/dev	Patch
create-remix	Patch
remix	Patch
@remix-run/architect	Patch
@remix-run/cloudflare	Patch
@remix-run/cloudflare-pages	Patch
@remix-run/cloudflare-workers	Patch
@remix-run/css-bundle	Patch
@remix-run/deno	Patch
@remix-run/eslint-config	Patch
@remix-run/express	Patch
@remix-run/node	Patch
@remix-run/react	Patch
@remix-run/serve	Patch
@remix-run/server-runtime	Patch
@remix-run/testing	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

🤖 Hello there,

We just published version 2.3.0-pre.0 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[github-actions]

🤖 Hello there,

We just published version 2.3.0 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[JacobMGEvans]

Hey! I love this, we came across this https://discord.com/channels/856971667393609759/1171477346046447616

seems like the backend code is not reading the Secret key properly in some situations.
https://github.com/JacobMGEvans/remix-and-vite-repro
Repro routes:
http://localhost/:5173/working
http://localhost/:5173/not-working

[markdalgleish]

@JacobMGEvans You should be using process.env on the server rather than import.meta.env. In Remix I'd recommend avoiding import.meta.env entirely since it bakes the environment variables into the code rather than allowing them to be dynamic at runtime. Instead you should use process.env on the server, and if the client needs access to it, pass the required env vars to the client via the loader.