fix(frontend,devops): error boundaries & sentry context, code splitting, XSS sanitization, and commit hygiene (#1090, #1091, #1092, #1093) - #1106
Open
bitcoindev817-hue wants to merge 1 commit into
Conversation
…rge conflict artifacts (fixes SoroLabs#1090, SoroLabs#1091, SoroLabs#1092, SoroLabs#1093)
|
@bitcoindev817-hue Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
Someone is attempting to deploy a commit to the Ayomide Adeniran's projects Team on Vercel. A member of the Team first needs to authorize it. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #1090
Fixes #1091
Fixes #1092
Fixes #1093
Summary & Architectural Improvements
This PR resolves four production & architectural issues (#1090, #1091, #1092, #1093) across frontend resilience, bundle performance, input sanitization security, and repository hygiene.
1. Granular React Error Boundaries & Context-Enriched Sentry Tracking (Fixes #1090)
<ErrorBoundary section={widget-${widget.id}}>so an unhandled rendering exception in one card is isolated without crashing the page layout.ErrorBoundaryto automatically enrich Sentry exception reports withwalletProvider,networkId, andcontractAddressdiagnostic tags and extra context.frontend/app/components/__tests__/ErrorBoundary.test.tsxverifying crash isolation, Sentry tags, and recovery state reset.2. Code Splitting & Dynamic Lazy Loading of Heavy Cryptographic Modules (Fixes #1091)
ZKProverPanel) and complex dashboard components (TaskExecutionHeatmapEngine,RPCNodeHealthDashboard) to lazy-load vianext/dynamicwith animated loading fallbacks.frontend/next.config.tsfor@stellar/stellar-sdk,snarkjs,recharts, andreactflowwith WebAssembly module streaming enabled (asyncWebAssembly: true).prefetch={true}to high-probability navigation paths (/dashboard,/tasks,/board,/keeper-metrics,/zk-prover) on the landing page and navigation menu.3. DOMPurify Sanitization on Dynamic Resolver Outputs & Markdown Renders (Fixes #1092)
sanitizeResolverOutputinfrontend/src/lib/sanitize.tsusing DOMPurify to strip script tags, event handlers (onload=,onerror=), andjavascript:URIs from dynamic resolver strings and task return values.SanitizedTaskOutputViewercomponent (frontend/components/SanitizedTaskOutputViewer.tsx) for safely rendering task execution return values in code blocks.MarkdownEditorto sanitize preview HTML viaDOMPurifybefore settingdangerouslySetInnerHTML.frontend/src/lib/__tests__/security-xss.test.tsxverifying neutralization of stored XSS vectors.4. Purge Leftover Git Merge Conflict Artifacts & Enforce Commit Hygiene (Fixes #1093)
conflicts_*.txt,merge_output_*.txt, andtest-rpc.jsdump files from the root repository directory.conflicts_*.txt,merge_output_*.txt, andtest-rpc.jsto.gitignore.scripts/check-conflict-markers.shto detect unresolved conflict markers (<<<<<<<,=======,>>>>>>>) in tracked files and exit with failure code 1..husky/pre-commitand GitHub Actions CI workflow (.github/workflows/e2e-integration.yml).Verification & Test Results
./scripts/check-conflict-markers.shpassed cleanly.npm run build) compiled successfully in 58s with route optimization and dynamic code splitting.