This repository was archived by the owner on Aug 27, 2026. It is now read-only.
Repository navigation
perf(content): exclude content from list page data - #98
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
Next.js build process showed a warning about large page data (>1MB) for list pages like
/updates:Cause
The
getStaticPropsfunction insrc/pages/[...slug].tsxwas callinggetAllMarkdownContentstwice:getRootLayoutPageProps(used to build the directory tree)./updates) to fetch child memos for the list page.Both calls loaded the full content of the markdown files into memory via
fs.readFileSyncwithingetAllMarkdownContents. This entire dataset, including content not needed for the directory tree or the list page view, was being serialized into the page props, causing the large data size.Solution
getAllMarkdownContents(src/lib/content/memo.ts):optionsobject parameter with anincludeContent: booleanflag (defaults totrue).contentproperty in the returnedIMemoItemobject ifincludeContentistrue.getStaticProps(src/pages/[...slug].tsx):getAllMarkdownContentsto pass{ includeContent: false }.buildDirectorTreeonly uses metadata.Expected Outcome
This change significantly reduces the amount of data included in the page props for directory list pages by excluding unnecessary markdown content. This should resolve the large page data warning and improve build performance and potentially runtime performance for these pages.