-
Notifications
You must be signed in to change notification settings - Fork 10
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
Route Based Code Splitting #265
Merged
Merged
Changes from 1 commit
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
c888286
feat: adding basic code splitting
hutchgrant 096a1d7
feat: adding app-template, removing dep, adding eslintignore
hutchgrant 9bb4009
feat: adding loading and spinner components, fix test
hutchgrant b1ea9e3
fix: dependencies removed
hutchgrant 7ad4e7e
fix: adjust chunk filenames
hutchgrant 210a982
feat: combine chunks based on page routes
hutchgrant e0a2a0d
feat: allow splitchunkplugin from config
hutchgrant 37d7f68
fix: condense optimization config
hutchgrant 047df37
Merge branch 'master' into feat/issue-136-code-splitting
hutchgrant eaf4aeb
Merge branch 'master' of github.com:ProjectEvergreen/greenwood into f…
hutchgrant 17305cb
fix: remove formatting issues
hutchgrant 4bfec57
fix: chunks arr and remove loading component
hutchgrant 8f5b7c1
fix: remove chunk optimization
hutchgrant d1f1144
fix: add min content height, stop footer flash
hutchgrant 949a1dc
remove forced formatting
thescientist13 a1bbfb2
Merge branch 'feat/issue-136-code-splitting' of github.com:ProjectEve…
thescientist13 097fedb
Merge branch 'master' into feat/issue-136-code-splitting
thescientist13 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, We should be doing this in webpack.config.common.js for the user by default.
And also do some sort of dynamic creation of
cacheGroups
here like we do in webpack.config.common.js withNormalModuleReplaclementPlugin
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking along the lines of similar to a plugin. If a developer wants custom split routes, they can configure it however they please. But I also agree we should be doing it by default as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I would still like to see this done dynamically generated based on the folders set in the users pages/ directory for now. Easy enough for us to make another issue for thinking about how to make it a public API, likely hand in hand with being able to allow our Graph to also go "deeper" than a depth of one: