Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to Next.js's app/ Directory #1579

Open
dysbulic opened this issue Jul 18, 2023 · 0 comments
Open

Migrate to Next.js's app/ Directory #1579

dysbulic opened this issue Jul 18, 2023 · 0 comments
Labels
feature request Feature Requests frontend Front end related issues / features

Comments

@dysbulic
Copy link
Member

What would you like to be added?

So, neither <CacheProvider> nor @emotion/server worked to end the FOUC.

The documentation for CacheProvider suggests that it useServerInsertedHTML only runs once in the pages/ directory structure, and it is before rendering is complete.

An option is to migrate to Next.js's app/ server-rendered directory structure.

The question is as to whether client-rendered component styles would be captured by this method. Since almost all our components rely on accessing a Context & components that use Context have to be client-side, it's entirely possible this won't help.

Why is this needed?

There is a second or more of unstyled content when the page first loads.

@dysbulic dysbulic added frontend Front end related issues / features feature request Feature Requests labels Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Feature Requests frontend Front end related issues / features
Projects
None yet
Development

No branches or pull requests

1 participant