Support for custom paths in tsconfig.json

[larsblumberg]

Problem

When configuring tsconfig.json with paths:

{
  "compilerOptions": {
    "baseUrl": "./",
    "paths": [
      "@fancyModules/*": ["./src/modules/fancyModule/*"]
    ]
  } 
}

the transpiler/loader used by threads wouldn't resolve these imports:

import { Thing } from "@fanceModules/things"

and thus lead to "module not found" errors.

Although this works perfectly when running the same code with ts-node / tsx.

Workaround

Do not use custom paths imports in any module that are directly or indirectly imported by a worker. Instead use relative imports for workers.

Related documentation

• https://www.typescriptlang.org/tsconfig/#paths
• https://www.typescriptlang.org/docs/handbook/modules/reference.html#paths

Possible support for threads?

Is there any change to get support for paths into threads?

[larsblumberg]

At least for a production build this package helps rewriting the imports: https://github.com/benyap/resolve-tspaths

However that still doesn't resolve the issue for dev builds using ts-node / tsx.