npm / tsc-alias
tsc-alias
What changed in tsc-alias 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-18.
1 new APIs and options3 behavior and defaults13 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli inittsc-alias 117 changes
New APIs and options 1
Automatically resolves import aliases across the entire project references graph when using tsc --build.
Behavior and default changes 3
Dynamic imports with Import Attributes / Options are now supported.
Import path resolution supports and strips .tsx, .jsx, .mts, .mjs, .cts, and .cjs extensions.
TypeScript wildcard mappings support suffixes in alias keys and target paths, as well as median wildcards.
Fixes and other changes 13
Aliases resolve to existing build artifacts.
resolveFullPaths can add extensions for module subpath imports.
Aliases between declaration files are now correctly resolved when using build with emitDeclarationOnly.
Avoids rewriting external imports that match empty directories when using baseUrl.
Fixes rewriting paths aliases outside rootDir that use ../.
Fixes alias rewriting when a sibling file and directory collide.
Fixes collisions between source files and node modules based on baseUrl.
Alias paths are resolved when baseUrl points to a nested subdirectory.
Path calculation and type alias resolution are fixed when declarationDir is nested inside outDir.
Project directory resolution in outDir uses ancestor suffix matching to prevent folder name collisions.
Path mapping now supports catch-all wildcard expressions.
Fixes unintended activation of baseurl mode.
Supports TypeScript 6 implicit baseURL so tsc-alias works with this configuration behavior.