Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug repro: Exports which shadow built-ins are incorrectly included in non-"complete" report variants #4761

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Josmithr
Copy link
Contributor

@Josmithr Josmithr commented Jun 5, 2024

This was not an issue prior to the reportVariants feature, but there are now cases where exports that are aliased to avoid conflicts with built-ins result in export statements being included in reports of incorrect release variants.

I updated one of the test scenarios to include an API export called "performance", which shadows a global. It is tagged as @internal. Note that in the non-"complete" report variants, an export for the item still occurs, while the aliased declaration is (correctly) omitted.

@@ -15,4 +15,6 @@ export class Lib2Class {
prop: number;
}

export { performance_2 as performance }
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that the declaration of performance_2 was omitted, but the de-aliased export is still included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs triage
Development

Successfully merging this pull request may close these issues.

None yet

1 participant