andywer / andywer/threads.js

Support for custom paths in tsconfig.json

未關閉
#493 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
TypeScript
星號
3.5k
分支
173
PR 合併指標
30 天內沒有已合併 PR

描述

# 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`?

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。