We no longer need to maintain the yarnWithEnv script. This probably wouldn't have been a big deal since it's unlikely we'd need to change it.
The yarnWithEnv script is potentially a strange thing to have in someone's repo. If someone creates a Bison app, it might not make sense why yarnWithEnv is there or how it's working.
The current setup, with setting DOTENV_CONFIG_PATH=.env.test, makes it impossible to override values in .env.test with a .env.test.local file (e.g. if you want to use a different database url, etc.).
Changes
Remove the yarnWithEnv script and replace it with dotenv-cli
There are a few reasons for this change:
yarnWithEnvscript. This probably wouldn't have been a big deal since it's unlikely we'd need to change it.yarnWithEnvscript is potentially a strange thing to have in someone's repo. If someone creates a Bison app, it might not make sense whyyarnWithEnvis there or how it's working.DOTENV_CONFIG_PATH=.env.test, makes it impossible to override values in.env.testwith a.env.test.localfile (e.g. if you want to use a different database url, etc.).Changes
yarnWithEnvscript and replace it withdotenv-cliChecklist