Skip to content

Improve frontend runtime and service performance - #734

Draft
dimaip wants to merge 4 commits into
dimaip/frontend-modernization-foundationsfrom
dimaip/frontend-performance-runtime
Draft

Improve frontend runtime and service performance#734
dimaip wants to merge 4 commits into
dimaip/frontend-modernization-foundationsfrom
dimaip/frontend-performance-runtime

Conversation

@dimaip

@dimaip dimaip commented Aug 6, 2026

Copy link
Copy Markdown
Owner

Stack

This is PR 2 of 3 and targets the preceding foundations branch. Merge the stack from the bottom up.

  1. Frontend foundations and tooling — #733
  2. Frontend runtime and service performance — this PR
  3. Performance measurement and evidence harness — #735

What changed

  • Replaces TOC polling and random heading IDs with a deterministic, batched heading registry.
  • Adds stable accessible heading labels and preserves heading order, levels, anchors, and duplicate handling.
  • Adds cached Suspense-based MDX loading with failure recovery and removes repeated per-fragment effects.
  • Reduces duplicate calendar/readings queries through explicit freshness policies and stable query keys.
  • Defers optional route, menu, editor, and service work until it is needed.
  • Adds production-style static delivery with precompressed immutable assets and cache-policy verification.
  • Adds a reproducible long-service benchmark, service regression budgets, and field performance marks.
  • Records and rejects progressive rendering/chunking variants that did not produce a defensible win.

Why

Long services were paying avoidable polling, repeated subscriptions, duplicate loading, and inactive-feature costs. These changes target measured CPU, render, and delivery bottlenecks while keeping the complete-document contract intact.

Impact and constraints

  • Service-worker source and offline corpus behavior are unchanged.
  • Dynamic MDX loading, parallel language mode, TOC navigation, print, search, copy/select-all, zoom, theme, and scroll restoration remain covered.
  • No custom-select replacement is included.
  • Chunking changes were retained only where the service and offline measurements supported them.

Validation

  • Deterministic TOC and heading-label unit coverage.
  • MDX contract, cache, runtime, query-policy, and static-delivery tests.
  • Browser E2E coverage for service, language, TOC, search, offline, and error-boundary behavior.
  • Production-build bundle reports and repeated long-service benchmark artifacts.

@vercel

vercel Bot commented Aug 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
calendar Ready Ready Preview Aug 6, 2026 2:19pm

# Conflicts:
#	Dockerfile
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant