-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle dynamic/destructured .dotenv variable access in main #57
Comments
Hi, how exactly are you using env variables in main? I have a feeling there might be an issue with env variable destructuring |
In the main I look through I looked at the output of After further investigation, I realized that my logic for getting an env variable from the main was actually located under another folder I can work around this short term but it would be nice to understand what's going on.. |
Yeah, if you don't use the variables directly, but rather dynamically or via destructuring it won't work (evanw/esbuild#438 (comment)). I might look later around for newer techniques to handle this better. |
ok thanks for the pointers. That's a shame that esbuild does not handle this correctly out of the box 😢 |
Hey 👋 ! Great work, thank you for this project!
I noticed that .env files are correctly read in dev mode in the main, but not in production (using
yarn try
for ex). Any idea on how I could make this work?Thanks a lot 🙏
The text was updated successfully, but these errors were encountered: