/
githubmirror
/
next.js
Обзор
Документация
Войти
/
githubmirror
/
next.js
Код
Запросы
0
Пакеты
0
Релизы
0
Аналитика
Безопасность
canary
errors/non-standard-node-env.mdx
31 строка
1 KB
Delba de Oliveira
docs: Migrate error messages to MDX and App Router. (#52038)
05 июл 2023, 16:11
Не верифицирован
05 июл 2023, 16:11
44d1a1c
Код
Авторство
О чём код?
--- title: 'Non-Standard `NODE_ENV`' --- ## Why This Error Occurred Your environment has a non-standard `NODE_ENV` value configured. This may be by accident, so if you're unaware where the value is coming from, check the following: - The `.env*` files in your project, if present - Your `~/.bash_profile`, if present - Your `~/.zshrc`, if present The greater React ecosystem treats `NODE_ENV` as a convention, only permitting three (3) values: - `production`: When your application is built with `next build` - `development`: When your application is run with `next dev` - `test`: When your application is being tested (e.g. `jest`) Setting a non-standard `NODE_ENV` value may cause dependencies to behave unexpectedly, or worse, **break dead code elimination**. ## Possible Ways to Fix It To fix this error, identify the source of the erroneous `NODE_ENV` value and get rid of it: Next.js automatically sets the correct value for you. If you need the concept of different environments in your application, e.g. `staging`, you should use a different environment variable name like `APP_ENV`. ## Useful Links - [Environment Variables](https://en.wikipedia.org/wiki/Environment_variable)