Set up Node Test Runner with TypeScript and ENV variables

.env

EXAMPLE_SECRET="12345"

.env.test

EXAMPLE_SECRET="6789" # Overwrites the .env one

README.md

For a detailed guide, check my article (100% free, forever)

Expected folder structure

ts-project/
├── tsconfig.json
└── apps/
    └── app-1/
        ├── tsconfig.json
        ├── package.json
        └── test/
            └── tsconfig.json

Install

# Use whatever package manager you prefer
pnpm add -D tsx glob

# For a single app in a monorepo
# pnpm add -F your-app -D tsx glob

# For the global package.json in a monorepo
# pnpm add -wD tsx glob

package.json

"scripts": {
	//...
	"test": "glob -c \"tsx --env-file .env --env-file .env.test --test --test-reporter spec \" \"./test/**/*.test.ts\"",
	//...
}

test.tsconfig.json

// RENAME TO `test/tsconfig.json` - Gists don't allow '/' in the filename
{
	"extends": "../tsconfig.json", // Can also extend the base monorepo config
	"compilerOptions": {
		"noEmit": true,
		"allowImportingTsExtensions": true
		// These don't work with Node Test Runner, but do with Bun. Purely optional QoL
		// "baseUrl": ".", 
		// "paths": {
		//	"@src/*": ["../src/*"]
		// },
	},
	"include": ["./**/*"]
}

tsconfig.json

// Needed because VS Code and other IDEs
// use it to decide which files to
// apply the base config's rules
{
	"extends": "../../tsconfig.json", // Base monorepo tsconfig
	"compilerOptions": {
// 		If "outDir": "${configDir}/dist", not already present
// 		in the base config. Otherwise you can delete `compilerOptions`
		"outDir": "./dist"
	},
	"include": ["./src/**/*"],
}