Remove section about ES modules and tree-shaking #3410
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.
In practice, tree-shaking does not currently allow for the kind bundle size reduction achievable using direct module imports, so shouldn't encourage it as an option for minimizing bundle size.
@Rich-Harris explains it here: reduxjs/redux#1369 (comment).
Specifically, because of the way we set up the singleton histories, those will not tree-shaken out, as noted by @tomduncalf in #3387 (comment).
The best approach then is to import from the ES module directory, but I don't think we should encourage people to import from
react-router/es6/*
when we want to move that toreact-router/es/*
. Maybe we should maintain an ES module build in both/es
and/es6
.