Use tsx watch mode and inject DB URL into .env.example

[dmitriyeff]

Summary

• Switch dev script from tsx src/index.ts to tsx watch --env-file=.env src/index.ts for hot reload and automatic env loading
• Inject database-specific DATABASE_URL examples into generated .env.example using options.projectName and the selected database dialect
• Add generated startup retry logic so npm run dev waits up to 60 seconds for the database and migrations before starting Express
• Improve generated MySQL connectivity by setting Drizzle MySQL mode: default, moving local MySQL host access to 127.0.0.1:3307, and aligning .env.example with that port
• Split generated Docker volumes into postgres_data and mysql_data so switching database choices does not reuse incompatible local data directories
• Suppress benign Postgres duplicate schema/table NOTICE logs from Drizzle migration startup while preserving other Postgres notices

Database startup behavior

• Postgres keeps localhost:5432 and uses a postgres_data Docker volume
• MySQL uses localhost:3307 on the host, maps to container port 3306, and uses a mysql_data Docker volume
• Generated src/index.ts retries runMigrations() once per second for up to 60 attempts, then starts the server only after migrations succeed
• Generated Postgres clients filter migration NOTICE codes 42P06 and 42P07, so repeated npm run dev starts do not print noisy “already exists, skipping” objects

Test plan

• npx vitest run src/generators/node/projectBuilder.test.ts src/generators/node/database.test.ts
• npm run typecheck
• npm run lint
• npm run build
• Verified generated app startup retry by starting npm run dev with the DB stopped, then starting the DB and confirming the same process reached Server running on port 3000
• Verified generated Postgres and MySQL containers can start cleanly with separate volumes and apply migrations
• Verified repeated Postgres npm run dev startup no longer prints duplicate Drizzle migration NOTICE objects

[Copilot]

Pull request overview

Updates the Node project scaffolding to improve local development ergonomics by enabling tsx hot-reload watch mode (with env loading) and by generating a dialect-specific DATABASE_URL example in .env.example based on the selected database and project name.

Changes:

• Switch generated package.json dev script to tsx watch --env-file=.env src/index.ts.
• Generate a database-dialect-specific DATABASE_URL example in .env.example using options.projectName and options.database.

Comments suppressed due to low confidence (1)

src/generators/node/projectBuilder.ts:95

• The generated package.json dev script was changed to use tsx watch --env-file=.env ..., but there’s no test coverage asserting the generated scripts. Consider extending an existing generator test to parse package.json and verify the dev script value so changes to the CLI invocation don’t silently break scaffolds.

		const pkg = {
			name: options.projectName,
			version: '0.1.0',
			type: 'module',
			scripts: {
				'dev': 'tsx watch --env-file=.env src/index.ts',
				'build': 'tsc',
				'typecheck': 'tsc --noEmit',
				'db:migrate': 'drizzle-kit migrate',
			},

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dmitriyeff]

It is validated and trimmed:

export async function promptProjectName(initial?: string): Promise<string> {
	const value = await clack.text({
		message: 'Project name or path?',
		initialValue: initial,
		validate: (v) => {
			const trimmed = v.trim();
			if (!trimmed) return 'Project name is required';
			if (!basename(trimmed)) return 'Path must include a directory name';
		},
	});

	if (clack.isCancel(value)) {
		clack.cancel('Operation cancelled');
		process.exit(0);
	}

	return (value as string).trim();
}

[youssef-saber-3]

do we need \ if we're using backticks ` ?

[dmitriyeff]

needed in the generator