tsconfig-paths

const tsConfig = require('./tsconfig.json'); const { register } = require('tsconfig-paths'); // Example tsconfig.json content: // { // "compilerOptions": { // "baseUrl": ".", // "paths": { // "@utils/*": ["src/utils/*"], // "@config": ["src/config/index.ts"] // } // } // } // 1. Using the CLI with Node.js: // To run a JavaScript file compiled from TypeScript with path aliases: // node -r tsconfig-paths/register main.js // 2. Using the CLI with ts-node: // To run a TypeScript file directly with path aliases: // ts-node -r tsconfig-paths/register main.ts // 3. Programmatic registration for more control: // This is useful if your tsconfig.json is not in the CWD or you need custom settings. const baseUrl = process.env.TS_NODE_BASEURL ?? tsConfig.compilerOptions.baseUrl ?? './'; const cleanup = register({ baseUrl, paths: tsConfig.compilerOptions.paths }); console.log('tsconfig-paths registered successfully.'); // Your application logic that uses path aliases would go here. // For example, if you had '@utils/logger' mapped to 'src/utils/logger.ts' // import { log } from '@utils/logger'; // log('Application started'); // When path registration is no longer needed (e.g., in a long-running process that might reconfigure) // cleanup();