Frontend Performance guidelines - #159
Open
MajorLift wants to merge 4 commits into
Open
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Frontend Performance Optimization Guidelines
Note
Low Risk
Low risk: documentation-only change with no runtime or build impact, though teams may adopt recommended patterns over time.
Overview
Adds a new
docs/frontend-performance.mdguide documenting high-impact React/Redux performance anti-patterns (e.g.,useSelector(..., isEqual),JSON.stringifyin deps, excessivecreateDeepEqualSelector, index keys) and recommended fixes (memoization, selector design, virtualization, lazy-loading, effect hygiene).Includes a prioritized audit-oriented checklist with links to tracking issues plus a section on React Compiler considerations and when manual memoization is still needed.
Written by Cursor Bugbot for commit 4411ca5. This will update automatically on new commits. Configure here.