Mot
@tianhuil if downgrading fixes for you let me know - and then I'll try to solve for both supporting vercel middleware and static builds - while still supporting dynamic import...
@tianhuil `1.48.4` should fix your problem. sorry about that. was probably affecting many users. https://github.com/dotenvx/dotenvx/compare/v1.48.3...v1.48.4
I'm still hesitant to get into traversal - because it introduces so many edge cases. I'll give this more thought. I appreciate the well written issue.
Thanks for doing the digging on this @jedwards1211. I'll try and look at this soon but could be a while.
Will do this but it will probably be a year from now. My rule of thumb has been to wait on this as long as possible (with dotenv also) because...
> but not versions that are only covered by commercial support Interesting. Could you expand on this idea a bit more?
Which deployment mechanism are you using with them? One of their services still does wonky things with environment variables.
I mean are you using their edge runtime? It has quirks around being able to inject environment variables.
Upvoting this discussion on Next.js could help - https://github.com/vercel/next.js/discussions/81605
@githubusername2022 is there a reason you're using edge rather than the normal runtime? Edge can't do basic things like read a file - so typically people using edge will build...