If an envrc exports environment variables that do not add or shadow existing commands, but are rather meant to mutate behavior of existing global commands, quickenv will not export those environment variables correctly.
An example of this is sentry's crash-reporting. sentry installs sentry-cli globally (using its own installer), and then exports a SENTRY_DSN environment variable that configures sentry-cli to report crashes to a particular server:
curl ... | sh # install sentry-cli in global PATH
export SENTRY_DSN=... # configure sentry-cli to report errors
Since sentry-cli is not exposed via a new PATH entry, quickenv will not shim it automatically, and as such sentry-cli will not run with SENTRY_DSN in its envvars.
There are multiple workarounds:
Use quickenv vars or quickenv exec explicitly.
Run quickenv shim sentry-cli.
Change the .envrc to install sentry-cli into a new directory, and add a new PATH entry that contains the new binary.
If an envrc exports environment variables that do not add or shadow existing commands, but are rather meant to mutate behavior of existing global commands, quickenv will not export those environment variables correctly.
An example of this is sentry's crash-reporting. sentry installs sentry-cli globally (using its own installer), and then exports a SENTRY_DSN environment variable that configures sentry-cli to report crashes to a particular server:
Since sentry-cli is not exposed via a new PATH entry, quickenv will not shim it automatically, and as such sentry-cli will not run with SENTRY_DSN in its envvars.
There are multiple workarounds:
quickenv varsorquickenv execexplicitly.quickenv shim sentry-cli..envrcto install sentry-cli into a new directory, and add a new PATH entry that contains the new binary.