You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you can tell bun to load an .env.* file with --env-file which is really nice, but sometime you just want to pass a single env var to a command to change the behaviour. The guide for env vars tells you to pass a single env var before the command. This works well on unix based systems, but for windows you need to install a separate package like cross-env to pass an env var to a command. Would be a nice to have if this can be build into bun run.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently you can tell bun to load an .env.* file with --env-file which is really nice, but sometime you just want to pass a single env var to a command to change the behaviour. The guide for env vars tells you to pass a single env var before the command. This works well on unix based systems, but for windows you need to install a separate package like cross-env to pass an env var to a command. Would be a nice to have if this can be build into bun run.
Beta Was this translation helpful? Give feedback.
All reactions