rsnext/errors/missing-env-value.md
JJ Kasper d8155b22ff
Add initial support for new env handling (#10525)
* Add initial support for new env config file

* Fix serverless processEnv call when no env is provided

* Add missing await for test method

* Update env config to .env.json and add dotenv loading

* ncc dotenv package

* Update type

* Update with new discussed behavior removing .env.json

* Update hot-reloader createEntrypoints

* Make sure .env is loaded before next.config.js

* Add tests for all separate .env files

* Remove comments

* Add override tests

* Add test for overriding env vars based on local environment

* Add support for .env.test

* Apply suggestions from code review

Co-Authored-By: Joe Haddad <joe.haddad@zeit.co>

* Use chalk for env loaded message

* Remove constant as it’s not needed

* Update test

* Update errsh, taskr, and CNA template ignores

* Make sure to only consider undefined missing

* Remove old .env ignore

* Update to not populate process.env with loaded env

* Add experimental flag and add loading of global env values

Co-authored-by: Tim Neutkens <timneutkens@me.com>
Co-authored-by: Joe Haddad <joe.haddad@zeit.co>
2020-03-26 13:32:41 +01:00

731 B

Missing Env Value

Why This Error Occurred

One of your pages' config requested an env value that wasn't populated.

// pages/index.js
export const config = {
  // this value isn't provided in `.env`
  env: ['MISSING_KEY'],
}
// .env (notice no `MISSING_KEY` provided here)
NOTION_KEY='...'

Possible Ways to Fix It

Either remove the requested env value from the page's config, populate it in your .env file, or manually populate it in your environment before running next dev or next build.