Whats needed for basic SSR?

Is your feature request related to a problem? Please describe. I want to render out the images server-side, perhaps with a css overflow to prevent a long list of images floating down the page while CSR hydrates

Describe the solution you’d like The ability to no execute the specific method, or render the function that causes SSR to fail

Describe alternatives you’ve considered Forking, but id rather help maintain than help fragment a good project

Additional context I wrote most the SSR mechanics that next.js dynamic is based off of and wrote the first code-split SSR utility back in the day. I know my way around SSR, just want to know what the issue is and will you accept the change if i burn time doing it.

[ScriptedAlchemy]

Understandably so, and I do see where you are coming from too! (I’ve got 20 million active users dependent on my OSS stuff)

I didn’t realize this was maintained by a company, that’s good to know! Looking at this from a risk mitigation aspect, free OSS maintainers often get bogged down which becomes a risk to companies if they cant get responses or merges from authors.

I feel way more comfortable knowing this is backed by a company. No need for maintainership unless you see a reason, happy to leave it in your hands and contribute 😃

Will take a look at SSR once our UX department finalizes all the varients of a carousel in the DSM. I’m planning to use yours as the standardized carousel sitewide. If I’ve got some time, ill make an early start on SSR and see where we get it too.

Great work on this carousel, one of the cleanest I’ve come across. Big kudos

[piotr-s-brainhub]

@ScriptedAlchemy

So I close this issue and the SSR feature request is reported there https://github.com/brainhubeu/react-carousel/issues/376