Mot

also what kind of KEYS in the file you are loading? maybe there is some weird self-referential thing going on that is very edge case and hasn't been accounted for...

``` Setting log level to debug process command [env] options: {"env":[],"envFile":["./.env"],"envVaultFile":[],"overload":true} loading env from ./.env (/home/bun/app/.env) {"ENV_MODE":"dev", ...} ENV_MODE set ENV_MODE set to dev ... [[email protected]] injecting env (12) from...

> I thought you reproduced it with bunx @dotenv/dotenvx run --overload -- env no, i cannot reproduce this at all. https://github.com/user-attachments/assets/ff940b71-b543-460d-b2aa-ed9d97dfe1f2 if you run the `env` command by itself do...

> but it also doesn't decrypt. dotenv-cli is a totally different cli. it doesn't encrypt or decrypt at all. > `dotenv-cli` doesn't have the same error wait, so does it...

ok, thank you, i will try there and see if i can reproduce.

can you share your Dockerfile contents actually? just redact anything sensitive.

one of the few references to `this._streamErr` happens to be `tinyexec` - which we switched to after `1.7.0` https://github.com/search?q=%22this._streamErr%22&type=code https://github.com/dotenvx/dotenvx/blob/main/CHANGELOG.md#changed-7

I've updated the Vercel guide to use `dotenvx.get`. It also mentions that you can alternatively deploy from the UI rather than from the cli. All looking good, so I'm going...

if using pages router you can do something like this: ``` import * as dotenvx from '@dotenvx/dotenvx'; export default function Page({ hello }: { hello: string }) { return Hello...

current `pro` addition. i've moved a lot of the extra features under `ext` (extensions). this way extensions can grow independtly of `dotenvx`'s core `oss` features: * run * get *...