You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 8, 2021. It is now read-only.
By making all the styles pages/_app.js available globally, the browser then must download and cache the entire file the first time. Is it different from the Next's default CSS-in-JS where a component has it's own CSS and it only loads when the component it's mounted.
How the difference between them would be? Is it worth?
The text was updated successfully, but these errors were encountered:
paperfella-ceo
changed the title
An entire global style against Next's default CSS-inJS
An entire global style against Next's default CSS-in-JS
Mar 27, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
By making all the styles
pages/_app.js
available globally, the browser then must download and cache the entire file the first time. Is it different from the Next's default CSS-in-JS where a component has it's own CSS and it only loads when the component it's mounted.How the difference between them would be? Is it worth?
The text was updated successfully, but these errors were encountered: