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
Please prefix the issue title with the project name i.e. [rush], [api-extractor] etc.
Is this a feature or a bug?
Feature
Bug
Please describe the actual behavior.
If we use "import Foo = Bar.Baz" syntax for external package, dts rollup will treat those symbols as local symbols, and produce incorrect dts result.
If the issue is a bug, how can we reproduce it? Please provide detailed steps and include a GitHub branch if applicable. Your issue will get resolved faster if you can make it easy to investigate.
This syntax may be weird, but it's very useful if an external package has exports with multiple hierarchies.
BTW I've been little confused recently about different import/export syntax.
There're some discussions like microsoft/TypeScript#7185 (comment), and official Modules document. But I didn't find the description for import Foo = Bar.Baz; syntax. The most similar case is import Foo = require('bar'), and they both have the same syntax kind "ImportEqualsDeclaration".
Please prefix the issue title with the project name i.e. [rush], [api-extractor] etc.
Is this a feature or a bug?
Please describe the actual behavior.
If we use "import Foo = Bar.Baz" syntax for external package, dts rollup will treat those symbols as local symbols, and produce incorrect dts result.
If the issue is a bug, how can we reproduce it? Please provide detailed steps and include a GitHub branch if applicable. Your issue will get resolved faster if you can make it easy to investigate.
With following
"foo"
package definition:And following dts file:
Dts rollup by api-extractor will generator following dts result:
The
"Class_inside_foo "
declaration should be an external import, but instead it's treated as local declaration here.What is the expected behavior?
May produce something like:
If this is a bug, please provide the tool version, Node.js version, and OS.
The text was updated successfully, but these errors were encountered: