file referenced by env_from not existing should not stop devbox enabling the environment

[t-monaghan]

What happened?

I get a papercut on first time use of projects using devbox's env_from where the typically untracked file doesn't exist, and due to this devbox will exit early. This can be frustrating as it doesn't provide the chance to ensure this file exists with a script in the init_hook. I understand that parsing env_from prior to executing the scripts in init_hook is required, but I would expect that if the files referenced by env_from do not exist devbox might print a warning, and continue setting up the environment.

Steps to reproduce

1. devbox init && devbox generate direnv
2. echo "somevar=" >> .private.example
3. echo '{
   "$schema": "https://raw.githubusercontent.com/jetify-com/devbox/0.13.7/.schema/devbox.schema.json",
   "env_from": ".private.env",
   "shell": {
   "init_hook": "cp -n .private.example .private.env"
   }
   }' > devbox.json

Results in the below

direnv: loading ~/dev/scratch/.envrc
direnv: using devbox
Info: Ensuring packages are installed.

Error: failed parsing .private.env file. Error: failed to open file: /Users/tom.monaghan/dev/scratch/.private.env

Command

shell

devbox.json

{
  "$schema": "https://raw.githubusercontent.com/jetify-com/devbox/0.13.7/.schema/devbox.schema.json",
  "env_from": ".private.env",
  "shell": {
    "init_hook": "cp -n .private.example .private.env"
  }
}

Devbox version

0.13.7

Nix version

nix (Nix) 2.24.10

What system does this bug occur on?

macOS (Apple Silicon)

Debug logs

No response