You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
package-b also contains a single root export, which is simply a re-export of namespace A from package-a.
It is also configured with package-a specified in its bundledPackages.
Its export looks like this:
export{A}from'package-a';
I would expect package-b's type roll-up to look identical to that of package-a, but instead, a malformed rollup is generated:
exportdeclarenamespaceA{{Foo,bar,Baz;}}export{};
Notice that the necessary imports are missing for Foo, bar, and Baz.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
Summary
See this repo for a repro of the issue: https://github.com/Josmithr/api-extractor-playground/tree/re-export-module-namespace
The repo contains 2 packages,
package-a
andpackage-b
.package-b
depends onpackage-a
, and both are configured with API-Extractor.In this scenario,
package-a
contains a single root export, which is a "namespace" generated via:It's type rollup, generated by API-Extractor looks like this:
package-b
also contains a single root export, which is simply a re-export of namespaceA
frompackage-a
.It is also configured with
package-a
specified in itsbundledPackages
.Its export looks like this:
I would expect
package-b
's type roll-up to look identical to that ofpackage-a
, but instead, a malformed rollup is generated:Notice that the necessary imports are missing for
Foo
,bar
, andBaz
.Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/api-extractor
version?node -v
)?The text was updated successfully, but these errors were encountered: