e9506773a3
This ensures we load all env values before loading `next.config.js` since these values can be used in there. This also updates to ensure we're testing these values are available while loading `next.config.js` so we don't regress on this. Fixes: https://github.com/vercel/next.js/issues/22811
18 lines
No EOL
697 B
Bash
18 lines
No EOL
697 B
Bash
PROCESS_ENV_KEY="env"
|
|
ENV_FILE_KEY=env
|
|
ENV_FILE_EMPTY_FIRST=
|
|
ENV_FILE_LOCAL_OVERRIDE_TEST=env
|
|
ENV_FILE_DEVELOPMENT_OVERRIDE_TEST=env
|
|
ENV_FILE_DEVELOPMENT_LOCAL_OVERRIDEOVERRIDE_TEST=env
|
|
ENV_FILE_PRODUCTION_OVERRIDEOVERRIDE_TEST=env
|
|
ENV_FILE_PRODUCTION_LOCAL_OVERRIDEOVERRIDE_TEST=env
|
|
ENV_FILE_TEST_OVERRIDE_TEST=env
|
|
ENV_FILE_TEST_LOCAL_OVERRIDEOVERRIDE_TEST=env
|
|
NEXT_PUBLIC_TEST_DEST=another
|
|
ENV_FILE_EXPANDED=$ENV_FILE_KEY
|
|
ENV_FILE_EXPANDED_CONCAT=hello-${ENV_FILE_KEY}
|
|
ENV_FILE_EXPANDED_ESCAPED=\$ENV_FILE_KEY
|
|
ENV_FILE_KEY_EXCLAMATION="hello!"
|
|
ENV_FILE_PROCESS_ENV="env-file"
|
|
ENV_KEY_IN_NEXT_CONFIG="hello from next.config.js"
|
|
NEXT_PUBLIC_ENV_KEY_IN_NEXT_CONFIG="hello again from next.config.js" |