Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[api-extractor] Fails to parse `bundledPackages` declarations from dir import

未关闭
#5,412 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
typescript
领域
tooling

调研方向

Start in ExportAnalyzer.ts, focusing on TypeScriptInternals.getResolvedModule and how the resolved module data is used for bundledPackages checks. Use the linked reproduction repository with the bundledPackages and directory-import example, then verify that the generated declaration contains an inlined export declaration rather than an import from './bar-dir'.

由索引模型根据 Issue 内容生成。

描述

Summary

When using bundledPackages options, import declaration from dir generates incorrect dts result.

e.g. configure "bundledPackages": ["foo"], with following foo package files:

  • index.d.ts
    export { Bar } from './bar-dir';
    
  • bar-dir/index.d.ts
    export interface Bar {}
    

and following entry dts file:

export * from "foo";

generates dts result:

import { Bar } from './bar-dir';
export { Bar }

Repro steps

Expected result:

Previous example should generate:

export declare interface Bar {}

or reproduce by: https://github.com/adventure-yunfei/api-extractor-issue--bundledPackages

Details

Debugged and found the reason, introduced by #3321. For import declaration from dir (e.g., import { A } from "./a", while resolved file is a/index.d.ts), TypeScriptInternals.getResolvedModule (in ExportAnalyzer.ts) returns the result without packageId data, thus bundledPackages check is skipped (cause bug here).

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question Answer
@microsoft/api-extractor version? 7.53.1
Operating system? Mac
API Extractor scenario? rollups (.d.ts)
Would you consider contributing a PR? No
TypeScript compiler version? 5.8.2
Node.js version (node -v)? v16.20.0
主要语言
TypeScript
星标
6.5k
派生
708
平均合并
4 天 13 小时
30 天内合并 PR
62

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/rushstack 的其他 Issue

查看 microsoft/rushstack 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。