θΏ™ζ˜―indexlocζδΎ›ηš„ζœεŠ‘οΌŒδΈθ¦θΎ“ε…₯任何密码
Skip to content

Conversation

@timothycarambat
Copy link
Member

Pull Request Type

  • ✨ feat
  • πŸ› fix
  • ♻️ refactor
  • πŸ’„ style
  • πŸ”¨ chore
  • πŸ“ docs

What is in this change?

Prevents lazy loading of Onboarding pages as when onboarding the user will be subjected to brief white flashes on the page as the lazy component is loaded in. This is not a great UX for the user and will allow onboarding to be a better first-impression of the application.

Additional Information

This has very minimal impact on the bunded size of the application.

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

@timothycarambat timothycarambat merged commit e973c1e into master Jan 16, 2024
@timothycarambat timothycarambat deleted the preload-onboarding branch January 16, 2024 22:15
@review-agent-prime
Copy link

frontend/src/App.jsx

While the changes made in the code are correct, they could potentially lead to performance issues. Importing the OnboardingFlow component directly, as opposed to using dynamic imports (lazy loading), can lead to longer initial load times as the browser has to download more data initially. This can be especially problematic for users with slower internet connections. I suggest reverting back to using dynamic imports for the OnboardingFlow component.
Create Issue
See the diff
Checkout the fix

    const OnboardingFlow = lazy(() => import("@/pages/OnboardingFlow"));
git fetch origin && git checkout -b ReviewBot/Impro-q4679oj origin/ReviewBot/Impro-q4679oj

cabwds pushed a commit to cabwds/anything-llm that referenced this pull request Jul 3, 2025
* no lazy onboarding

* no lazy onboarding steps

* Do not lazy load onboarding to prevent lazy-load white flash
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.

2 participants