Core Refactor - migrate to secondary entrypoints to optimize de bundle size #1141
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alecarn
changed the title
alecarn
changed the title
alecarn
force-pushed
the
1405--core-assembly-analysis-of-the-size-of-our-packages-and-strategies-to-optimize-them
branch
from
8249807
to
67c7dc1
Compare
alecarn
deleted the
1405--core-assembly-analysis-of-the-size-of-our-packages-and-strategies-to-optimize-them
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a refactor of how the core package is structured. We propose to compose with secondary entrypoint to enable a better tree shakable library. There will not be a visible difference for the igo2 application, but each application that only uses part of the lib will have a major gain over a reduced bundle size.
Linked PR in the igo2-lib project: infra-geo-ouverte/igo2-lib#1625