Consider Size component about dripsy HOT 6 CLOSED

While I'm using this my app, I'm still not sure if I'm convinced by it. I think getting rid of SSR (and thus fresnel) would be a better idea than entirely circumventing RNW altogether :/

from dripsy.

This seems pretty useful. I know I would personally use it, I think it cleans up the code quite a bit compared to the webContainerSx prop.

At the moment, the same thing is achieved by passing a webContainerSx prop. It's a bit cumersome and repetitive. I think it's a nice escape hatch prop to have, but for sizing, it makes more sense to have a specific solution.

I agree with this. It's not always intuitive right off the bat.

from dripsy.

While I'm using this app, I'm still not sure if I'm convinced by it. I think getting rid of SSR (and thus fresnel) would be a better idea than entirely circumventing RNW altogether :/

I would have to agree. Leaving out SSR would be a bummer but this would make the API a bit more intuitive.

from dripsy.

Yeah. And like I mentioned earlier, my app doesn't even have SSR. One of my providers delayed rendering until after mounting, so BeatGig has never even had SSR 😂

I spent all this time making Dripsy support SSR, only to find that I didn't even need it, because my site is fast enough without it. Also, it hasn't harmed us with Google at all.

I still use SSR for SEO meta tags, but I put these at the root before rendering any providers anyway, thanks to pages/_app.js from next.js.

from dripsy.

Yeah. And like I mentioned earlier, my app doesn't even have SSR. One of my providers delayed rendering until after mounting, so BeatGig has never even had SSR 😂

I spent all this time making Dripsy support SSR, only to find that I didn't even need it because my site is fast enough without it. Also, it hasn't harmed us with Google at all.

I still use SSR for SEO meta tags, but I put these at the root before rendering any providers anyway, thanks to pages/_app.js from next.js.

That's good to know. This makes me feel a little bit more comfortable building with Dripsy w/o the serverside features, plus most of the content would probably still render server-side (if it's the same on mobile/desktop), just wouldn't be styled correctly.

from dripsy.

Yeah, that's true. Although I would recommend returning null (or a placeholder) and then rendering the app after it's mounted if you ever plan on using responsive styles. I'll probably do this with an ssr prop on the provider.

Ultimately, we're dealing with constraints of RNW.

from dripsy.