Fix LFX 2026 build failure#7784
Closed
KatalKavya96 wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Kavya Katal <kavyakatal09@gmail.com>
Contributor
|
Member
Author
|
This change is no longer needed. |
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
1 participant
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.
Description
This PR fixes #7783
This PR fixes the production build failure on
/programs/lfx/2026.The build was failing during Gatsby static HTML generation with the following error:
The issue was caused by
ArrowUpwardIconbeing imported from@sistent/sistent, but that icon export appears to be unavailable/undefined. As a result, Gatsby attempted to render an undefined component during the production build.This PR removes the invalid icon import and replaces it with a simple arrow inside the existing back-to-top button, keeping the same functionality while avoiding the undefined component error.
Notes for Reviewers
Tested with:
The production build now completes successfully:
There are still existing
[gatsby-plugin-image] Missing image propwarnings during the build, but they do not block the build and appear unrelated to this specific failure.Signed commits