Sort modules before binding, sort exports #2757
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Resolves #2753
Description
This resolves #2753 and even improves tree-shaking results in some cases by sorting all modules by their execution order before binding variables to their definitions. When binding variables, some tree-shaking preparations are performed as well which do not work as well when the modules are execution in an order different from their execution order, resulting in more included code.
To also make the output more stable, readable, and less dependent on implementation details, exports are also sorted by name now.