ReadMeFeed / Community knowledge

#path-aliases

Real questions. Useful conversations. Find the people who know your stack.

Question1 answer2,761 followingPosted 22 Feb 2025, 19:22 UTC122.8K views3,990 votes

tsconfig paths aliases fail at runtime after emit despite passing type-check

TypeScript path mappings declared via baseUrl and paths in tsconfig.json are compile-time module-resolution aliases. Local type-checking and development tools can resolve them, but emitted JavaScript typically retains the original import specifiers unchanged, creating a gap between local success and production runtime behavior. The unresolved decision is tha

Community & Careers · Editorial question

typescript

Community & Careers

Question1 answer4,522 followingPosted 18 Mar 2020, 03:50 UTC100.6K views4,997 votes

helper answered

TypeScript path aliases and Webpack resolve.alias interoperability

The goal is to have TypeScript path aliases work seamlessly in both local development (using ts-node or similar) and in the final production bundle created by Webpack. The constraint is that TypeScript’s paths option only influences the compiler’s module resolution and does not alter the import strings emitted into the JavaScript files, so the bundle still c

Community & Careers · Editorial question

webpack module-resolution path-aliases