arethetypeswrong / arethetypeswrong/arethetypeswrong.github.io
feature: detect inferred type cannot be named error
- 主要语言
- TypeScript
- 星标
- 1.6k
- 派生
- 65
- PR 合并指标
- 30 天内没有已合并 PR
描述
I was thinking about doing something similar.
Basically what's need is to get the package, install the dependencies, and see if the types in the output files can be resolved or not.
This is especially problematic with `pnpm` with monorepo as the transient packages are located at the top level `./node_modules/.pnpm/...`.
For example:
```sh
# Dependency graph
- lib-a
- lib-b
- lib-c
```
```sh
# folder
- packages
- lib-a
- node_modules
- lib-b # symlink to /node_modules/.pnpm/lib-b/version-y
- node_modules
- .pnpm
- lib-b@version-y
- lib-c@version-x
```
If `lib-b` does not re-exports the type from `lib-c`, you will get Inferred type cannot be named error.
贡献指南
这个仓库没有索引到贡献指南
调研方向
该 issue 没有指出文件、测试或入口点。首先追踪 pnpm 单体仓库的包安装和输出类型解析,然后将完成定义为:检测出某个推断类型无法命名,因为传递依赖的类型没有被重新导出。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- typescript
- 领域
- tooling
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 20/100