Bug description
After upgrading to version 2.16.x [dotenv][DEBUG] logs started spamming the console with "did not match key" and "overwrite" warnings
[dotenv][DEBUG] did not match key and value when parsing line 32:
[dotenv][DEBUG] did not match key and value when parsing line 37:
[dotenv][DEBUG] did not match key and value when parsing line 40:
[dotenv][DEBUG] did not match key and value when parsing line 43:
[dotenv][DEBUG] did not match key and value when parsing line 47:
[dotenv][DEBUG] "NODE_ENV" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "BUILD_TARGET" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "PORT" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "LOG_LEVEL" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "LOG_DIFFERENCE" is already defined in `process.env` and will not be overwritten
[dotenv][DEBUG] "DEBUG" is already defined in `process.env` and will not be overwritten
...many more
How to reproduce
Upgrade from 2.15.0 to 2.16.x
Have existing DEBUG env variable set to unrelated namespace
Logs spam during nexus schema generation and logs spam during server start
Expected behavior
No logs
Prisma information
"prisma": "2.16.1",
"@prisma/client": "2.16.1",
// or
"prisma": "2.16.0",
"@prisma/client": "2.16.0",
Environment & setup
- OS:
- Database:
- Node.js version:
- Prisma version:
Bug description
After upgrading to version 2.16.x
[dotenv][DEBUG]logs started spamming the console with "did not match key" and "overwrite" warningsHow to reproduce
Upgrade from 2.15.0 to 2.16.x
Have existing
DEBUGenv variable set to unrelated namespaceLogs spam during nexus schema generation and logs spam during server start
Expected behavior
No logs
Prisma information
Environment & setup