Closed jonluca closed 1 day ago
would love to see a fix on this too!
breaking our next.js app
Same here.
It broke some of my apps too. The two workarounds I found were either to render the component on the client, or the package version needs to be downgraded to 2.2.0
.
Can you checkout v2.3.0
? It should resolve the issue
Can you checkout v
2.3.0
? It should resolve the issue
Thank you so much for the patch, checking now...
Looks like the SSR error is gone 🥳
Quick question: looks like ResponsiveMasonry
initially renders with 1 column, and then it kicks in and respects columnsCountBreakPoints
. This creates a Layout Shift, which dings a website's/PWA's SEO score (see Chrome Lighthouse or this article).
Is it possible to have ResponsiveMasonry
initially render using the values in columnsCountBreakPoints
, instead of defaulting to 1 initially?
It could be great! PR's are welcome if you want to help :)
It looks like GitHub does not have the latest version of the source code, but v2.2.1 broke SSR by having an unprotected window call during render