Expand $HOME directory shorthand ~ (tilde character) to absolute path

[DJviolin]

Is your feature request related to a problem? Please describe.

I'm using shdotenv in a special Laradock project structure, where I merge Laradock's and my environment variables into one:

eval "$($DIR/shdotenv --dialect docker --overload --env laradock.env.example || echo "exit $?")"
set -a && . ./.env && set +a

However, shdotenv cannot expand the tilde character, if I put the value in quote or not, doesn't matter:

eval "$($DIR/shdotenv --dialect posix --overload --env .env || echo "exit $?")"

Output I'm getting:

APACHE_SSL_PATH=~/.laradock/ssl/apache2

Expected output:

APACHE_SSL_PATH=/home/user/.laradock/ssl/apache2

Describe the solution you'd like

It would be nice to have a flag, where it can expand $HOME shorthand (~) to absolute paths.

Describe alternatives you've considered

The only working solution is to use the good old bash env variable parsing trick:

set -a && . ./.env && set +a

But with this, I loose every control over the file and I have to format it very carefully. It works with my files, but not with the ones from various repositories.

Additional context

None.