[DON'T MERGE] make client entry points explicit #466
Closed
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.
Hit a bug on a decently-sized app where a chunk wasn't being created for one of the dynamically imported entry points representing a specific page. It's something to do with Rollup's code-splitting algo — if I remove certain imports from the page in question it gets chunked up correctly — but I don't have the bandwidth to delve too deeply into it.
Luckily I don't need to — we can just be explicit about what the entry points are. Bonus: in doing so we can make the file structure of the build much more navigable.