Skip to content

Conversation

@weswigham
Copy link
Member

@weswigham weswigham commented Feb 14, 2020

This is a followup to #35967 based on this comment that causes us to still produce an assignment for exports without initializers, this way they can still be found by importers and have getters made for them. (92aeea3 is the unique commit in this PR)

@weswigham weswigham force-pushed the retain-undefined-initializations branch from 92aeea3 to 6f693aa Compare February 25, 2020 19:38
Copy link
Contributor

@rbuckton rbuckton left a comment

Choose a reason for hiding this comment

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

Just in case, undefined isn't valid in ES3.

Copy link
Contributor

@rbuckton rbuckton left a comment

Choose a reason for hiding this comment

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

This is adding an unnecessary exports.x = undefined for downlevel enums and modules, which includes the comments.

@weswigham weswigham requested a review from rbuckton February 25, 2020 23:54
@weswigham weswigham merged commit 454cdb8 into microsoft:master Feb 26, 2020
@weswigham weswigham deleted the retain-undefined-initializations branch February 27, 2020 21:59
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants