@hyperse/ts-node-paths

A package to bind paths alias, resolving the source directory when the app is launched with ts-node, or resolving the out directory when ts-node isn't used. Includes some utilities in case if you need to generate paths dinamically depending of the code that is running.

This package has been designed to work with ESM projects (using --loader flag).

With this package, you can forget about those ugly imports like:

1import { Jajaja } from '../../../../../../../jajaja.js';
2import { Gegege } from '../../../../../gegege.js';

...and instead you can use alias like this (with the power of intellisense):

1import { Jajaja } from '@alias-a/jajaja.js';
2import { Gegege } from '@alias-b/gegege.js';

Disclaimer

This package is designed to work in end-user backend aplications for unit-testing purpose (because of how module alias works). So this probably doesn't work in front-end applications, or apps that uses a bundler (like webpack for example).

Also, this package is experimental and probably can generate unexpected behaviors, or performance issues. For that reason, you must test intensively this package in all possible use cases if do you want to implement in production.

Installation

We don't need to installed ts-node, now is the moment:

just install this package as a dependency:

1npm i --save @hyperse/ts-node-paths

Usage

To explain all features of this package, we will use this project estructure as example:

1# Your current working directory
2project-folder
3│   # The project dependencies
4├── node_modules
5│
6│   # The transpiled files
7├── dist
8│   │   # The file when the app starts
9│   ├── index.js
10│   │
11│   ├── folder-a
12│   │   ├── ...
13│   │   └── ...
14│   ├── folder-b
15│   │   ├── ...
16│   │   └── ...
17│   └── ...
18│
19│   # The source code
20├── src
21│   │   # The file when the app starts
22│   ├── index.ts
23│   │
24│   ├── folder-a
25│   │   ├── ...
26│   │   └── ...
27│   ├── folder-b
28│   │   ├── ...
29│   │   └── ...
30│   ├── file-x.ts
31│   └── ...
32│
33│   # The project configuration files
34├── package.json
35├── package-lock.json
36└── tsconfig.json

Configure your tsconfig.json

This package reads the tsconfig.json file (and is capable to find values if the file extends another configuration files) to declare the alias. A typical configuration coul be similar to this:

1{
2  "compilerOptions": {
3    "rootDir": "./src",
4    "outDir": "./dist",
5
6    "baseUrl": "./src",
7    "paths": {
8      "@file-x": ["./file-x.ts"],
9      "@alias-a/*": ["./folder-a/*"],
10      "@alias-b/*": ["./folder-b/*"]
11    }
12  }
13}

ENV

Path to tsconfig file. Environment: TS_NODE_PATHS_PROJECT

1runTsScript(
2  program,
3  {
4    env: {
5      TS_NODE_PATHS_PROJECT: 'tsconfig.json',
6    },
7  },
8  ...args
9);

Enable verbose status messages by Environment: HYPERSE_TS_NODE_PATHS_VERBOSE

The fields listed in the example of above are all required in order to the correct working of the package.

with ESM type:module projects

• scripts (node 20+)

  1{
  2  "serve": "yarn node --import=@hyperse/ts-node-paths/register ./config/dev-server.ts"
  3}

Utilities

This package includes dotnet package, so if you want, create a .env file in your current working directory.

Function isTsNodeRunning

If you want to check if ts-node is running, you can execute this function:

1import { isTsNodeRunning } from '@hyperse/ts-node-paths';
2
3const response = isTsNodeRunning(); // Returns a boolean
4console.log('if ts-node is running?', response);

Function isPathAliasRunning

If you want to check if @hyperse/ts-node-paths is running, you can execute this function:

1import { isTsNodePathsRunning } from '@hyperse/ts-node-paths';
2
3const response = isTsNodePathsRunning(); // Returns a boolean
4console.log('if this package is running?', response);

Function pathResolve

Resolve any subfolder of "rootDir" depending if ts-node is running. For example, imagine do you want to resolve the path "./src/folder-a/*":

1import { pathResolve } from '@hyperse/ts-node-paths';
2
3const path = pathResolve('./folder-a/*');
4console.log('path:', path);

With ts-node the output is:

1node --loader @hyperse/ts-node-paths/esm ./src/index.ts
2node --import=@hyperse/ts-node-paths/register ./scripts/build.ts
3
4# path: src/folder-a/*

With the transpiled code:

1node --loader @hyperse/ts-node-paths/esm ./dist/index.js
2node --import=@hyperse/ts-node-paths/register ./dist/index.js
3
4# path: dist/folder-a/*

Optionally receives as second parameter an object with this options:

• "absolute":

  If true, returns the full path, otherwise returns the path relative to the current working directory.

• "ext":

  If true, converts the extensions *.ts / *.mts / *.cts / *.js / *.mjs / *.cjs depending if ts-node is running or not.

Limitations

• The library requires a "tsconfig.json" file into the current working directory to work. Doesn't matter if that file extends another file, or be a part of a set of inhetirance, while all required properties are accesible through its ancestors.

• The resolve output between "baseURL" and the "paths" declared in the "tsconfig.json" file must always return a path inside of "rootDir" folder.

• Recommand setup your tsconfig.json, baseUrl to ./

1{
2  "$schema": "https://json.schemastore.org/tsconfig",
3  "extends": "../../tsconfig.base.json",
4  "compilerOptions": {
5    // If the code contains import 'events' and it coincidentally matches the paths baseUrl /src/events directory,
6    // it may cause the built-in events module to be incorrectly resolved as a relative module of the project.
7    // NOTE: recommmand config baseUrl:'./' Instead of use `./src`
8    // Avoid run into issue of "builtin module `events` wrong resolved as `./src/events`"
9    "baseUrl": "./",
10    "allowJs": false,
11    "noEmit": false,
12    "incremental": true,
13    "paths": {
14      "@hyperse/testing": ["../../packages/testing/src/index.js"]
15    },
16    "types": ["vitest/globals"]
17  },
18  "exclude": ["**/node_modules", "**/.*/", "dist", "build"]
19}
20