[GH-ISSUE #24] Load dotenv files automatically or provide migration guide #7

New issue

Closed

opened 2026-05-06 12:36:25 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-06 12:36:25 +02:00

Owner

Originally created by @wojtekmaj on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/24

Either:

Load dotenv files automatically like Next.js does (.env.local, and so on), or:
Provide migration guide on how to re-implement this on top of Vite

Originally created by @wojtekmaj on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/24 Either: - Load dotenv files automatically like Next.js does (.env.local, and so on), or: - Provide migration guide on how to re-implement this on top of Vite

BreizhHardware closed this issue

2026-05-06 12:36:25 +02:00

BreizhHardware commented

2026-05-06 12:36:26 +02:00

Author

Owner

@wesleymatosdev commented on GitHub (Feb 24, 2026):

https://vite.dev/guide/env-and-mode#env-files this does not work @wojtekmaj?

@wesleymatosdev commented on GitHub (Feb 24, 2026): https://vite.dev/guide/env-and-mode#env-files this does not work @wojtekmaj?

BreizhHardware commented

2026-05-06 12:36:26 +02:00

Author

Owner

@wojtekmaj commented on GitHub (Feb 24, 2026):

Nope. As soon as I accessed the page after dev server has started, a crash (null check on missing env variable) occurred.

Changing the dev command to:

node --env-file=.env.local node_modules/.bin/vinext dev

worked around the issue.

@wojtekmaj commented on GitHub (Feb 24, 2026): Nope. As soon as I accessed the page after dev server has started, a crash (null check on missing env variable) occurred. Changing the dev command to: ``` node --env-file=.env.local node_modules/.bin/vinext dev ``` worked around the issue.

BreizhHardware commented

2026-05-06 12:36:27 +02:00

Author

Owner

@niicojs commented on GitHub (Feb 26, 2026):

I'm still not seeing process.env populated in my tests.
node / latest nextjs / latest vinext / windows

@niicojs commented on GitHub (Feb 26, 2026): I'm still not seeing process.env populated in my tests. node / latest nextjs / latest vinext / windows

BreizhHardware referenced this issue

2026-05-06 12:38:43 +02:00

[PR #7] [MERGED] fix: add 'use client' to next/dynamic shim for App Router RSC compatibility #240

BreizhHardware referenced this issue

2026-05-06 12:38:44 +02:00

[PR #8] [MERGED] chore: bump version to 0.0.2 #241