typescript-paths

[npm:latest]: https://www.npmjs.com/package/typescript-paths/v/latest
[npm:latest:badge]: https://img.shields.io/npm/v/typescript-paths/latest?style=flat-square

[![Latest Version][npm:latest:badge]][npm:latest]

Resolving tsconfig paths in runtime

``sh
npm install typescript-paths
`

`js
const { register } = require("typescript-paths")
register()
`

Example tsconfig.json

`json
{
"compilerOptions": {
"paths": {
"~/": ["./"]
}
}
}
`

Then you can import alias instead of annoying path

`js
// const App = require("../../../../App")
const App = require("~/App")
``

Options

$3

Specify the path where your TypeScript configuration file.

If not set:

- use Environment variable TS_NODE_PROJECT
- or search tsconfig.json in current working directory.

$3

Set the logging level on the plugin.

$3

The handler to handle unusual module name.

$3

Colorful ouput.

$3

reference

- https://www.typescriptlang.org/docs/handbook/module-resolution.html#path-mapping
- https://github.com/microsoft/TypeScript/issues/5039