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

Make sure unused default exports are deconflicted when not tree-shaking #2758

Merged
merged 1 commit into from Mar 20, 2019

Conversation

lukastaegert
Copy link
Member

This PR contains:

  • bugfix
  • feature
  • refactor
  • documentation
  • other

Are tests included?

  • yes (bugfixes and features will not be merged without tests)
  • no

Breaking Changes?

  • yes (breaking changes will not be merged unless absolutely necessary)
  • no

List any relevant issue numbers:
Resolves #2752

Description

The algorithm used when skipping tree-shaking did not include variables reflecting unused default exports which resulted in those exports being ignored for deconflicting.

@mislav
Copy link
Contributor

mislav commented Mar 19, 2019

Thank you for the fix! Confirmed that the patch enables us to import d3-shape, d3-geo modules with treeshake disabled and that the build produced is free of conflicts.

@lukastaegert lukastaegert merged commit 26d2b31 into master Mar 20, 2019
@lukastaegert lukastaegert deleted the gh-2752-deconflict-unused-default-exports branch March 20, 2019 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Conflicting variables generated from mix of regular and default module exports
2 participants