Mot
related: https://github.com/dotenvx/dotenvx/issues/316
going to sit on this for a bit as I think the last 3 fixes largely nullify the need for the original request. 1. decryption errors now bubble up to...
it's out. `1.10.2` is current latest. let me know how it goes. still considering the ability to directly pass privateKey as a flag/option, but probably will not prioritize it just...
it looks like dotenvx succeeded: ``` [[email protected]] injecting env (12) from ./.env ``` but that maybe your code is failing? ``` undefined is not a function (near '...o of this._streamErr...')...
oops, also make sure that is using `1.11.3` rather than 1.7.0 as you currently have it.
also i would guess that `bunx some-npm-module` probably won't work with bun's runtime. deno's is incompletely implemented currently for these ciphers and bun probably is too, being so young: https://github.com/dotenvx/dotenvx/issues/353...
yeah, does look like bunx works. nice! ``` echo "HELLO=world" > .env bunx @dotenvx/[email protected] encrypt bunx @dotenvx/[email protected] get bunx @dotenvx/[email protected] run -- env ``` trying your scenarios. this is likely...
``` echo "HELLO=production" > .env.production bunx @dotenvx/[email protected] encrypt -f .env.production bunx @dotenvx/[email protected] get -f .env.production bunx @dotenvx/[email protected] run -f .env.production -- env ``` ^ this all works correctly for me...
``` $ bunx --version 1.1.8 ```
``` # outputs the decrypted `env` followed by the undefined is not a function error bunx @dotenvx/[email protected] run --overload -f "$VAULT_FILE" -- env ``` what's this look like if you...