.env file for me sparing me the need to pollute my session with environment variables.
I've been using Fish shell for years which is great and all, but one thing that has got me frustrated is using it with .env files.
When attempting to run source .env in a project, I usually encounter this problem:
.env (line 2): Unsupported use of '='. In fish, please use 'set KEY value'.
from sourcing file .env
source: Error while reading file '.env'
This is because Fish wants environment variables to be exported with syntax set -gx KEY value instead of export KEY=valuein Bash and ZSH.
So, I added the envsource command into my functions. Ideally, I wouldn't have to do this as many projects use dotenv or similar library to read environment variables. Then again, many projects are not quite there.