Package Exports
- tsc-alias
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (tsc-alias) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
tsc-alias
Replace alias paths with relative paths after typescript compilation. You can add aliases that reference other projects outside your tsconfig.json project by providing a relative path to the baseUrl.
Comparison to tsconfig-paths
+ Compile time (no runtime dependencies)
Getting Started
First, install tsc-alias as devDependency using npm.
npm install -g tsc-aliasnpm install --save-dev tsc-aliasAdd it to your build scripts in package.json
"scripts": {
"build": "tsc --project tsconfig.json && tsc-alias -p tsconfig.json",
}
================ OR ===================
"scripts": {
"build": "tsc && tsc-alias",
"build:watch": "tsc -w & tsc-alias -w"
}API
Installation
npm install tsc-aliasUsage
import { replaceTscAliasPaths } from 'tsc-alias';
replaceTscAliasPaths(options?);Here are all the available options:
| Option | Description | Default Value |
|---|---|---|
| configFile | path to tsconfig.json | 'tsconfig.json' |
| watch | Observe file changes | false |
| outDir | Run in a folder leaving the "outDir" of the tsconfig.json (relative path to tsconfig) | tsconfig.compilerOptions.outDir |
| resolveFullPaths | Attempt to replace incomplete import paths (those not ending in .js) with fully resolved paths (for ECMAScript Modules compatibility) |
false |
| silent | Reduced terminal output | false |