Remove dotenv dependency

package.json

@@ -82,7 +82,6 @@
 		"ajv-keywords": "^5.1.0",
 		"cors": "^2.8.5",
 		"csv-parse": "^5.5.3",
-		"dotenv": "^16.3.1",
 		"express": "^4.18.2",
 		"express-jwt": "^8.4.1",
 		"graphile-worker": "^0.16.1",

src/logger.ts

@@ -1,14 +1,6 @@
-import dotenv from 'dotenv';
 import pino from 'pino';
 import type { Logger } from 'pino';
 
-// Calling dotenv.config() prior to creating a logger ensures that environment
-// variable LOG_LEVEL can be loaded from .env files. See
-// https://github.com/PhilanthropyDataCommons/service/issues/59#issuecomment-1197227254
-// and following. There may be a better place than including and calling dotenv
-// here in the logger code.
-dotenv.config();
-
 // To prevent replays with JWT, we can redact the signature. This invalidates the JWT.
 export const redactToPreventAuthReplay = (secret: string): string =>
 	secret.replace(/^(Bearer [A-Za-z0-9]*\.[A-Za-z0-9]*\.).*/, '$1[redacted]');

src/test/globalSetup.ts

@@ -1,19 +1,7 @@
 // Jest expects a single default function to be exported from this file.
 /* eslint-disable import/no-default-export */
-import dotenv from 'dotenv';
 import type { Config } from 'jest';
 
-// TODO: reconsider use of '.env.test' if or when
-// https://github.com/ThomWright/postgres-migrations/pull/93 gets merged/fixed.
-dotenv.config({ path: '.env.test' });
-
-// Production code will run dotenv.config() anyway, so make clear that it
-// happens by running the same explicitly here. If '.env.test' has any variables
-// set, they will override the later/inner set variables such as those in the
-// '.env' file. There might be a better way to manage 'dotenv' and pino logger
-// setup.
-dotenv.config();
-
 export default (globalConfig: Config, projectConfig: Config): void => {
 	if (
 		(process.env.LOG_LEVEL === undefined || process.env.LOG_LEVEL === '') &&