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
[v2] Remove SSR #101
[v2] Remove SSR #101
Conversation
Major version bump, to v2. Please test with |
Okay, I'm certainly experiencing some issues with this on web. Need to figure out why. Update: fixed |
Lol, just kidding. I was using |
I'll likely merge this today. All working great for me. |
Added validation for breakpoints in your theme |
Deprecated 🤯 |
Updated docs & example for Next.js apps. Should be ready to go. Will test a few more hours then merge. |
v2 published ( yarn add dripsy |
Close #100
Breaking Changes
ssr={true}
toDripsyProvider
. In this case, it'll delay rendering until the app mounts. If you already have a gate of your own, then this isn't needed.style
prop will no longer be themed. This will let you usestyle
to pass raw styles. This prop being themed was undocumented, and never recommended oversx
, so this shouldn't be a problem.SEO Recommendations
If you use custom meta tags for SEO, such as
next-seo
, don't make them the children ofDripsyProvider
. Instead, place them before the provider.I achieve this in Next.js by 1) passing an
seo
object fromgetStaticProps
to my page props, and then 2) inpages/_app.js
, I render<NextSeo {...pageProps.seo} />
outside of my providerAnd then use the
seo
it returns here: