is it ready for production?

[vasco3]

Hi @smeijer
Is this ready for production?

Can I use the getServerSideProps in per component basis or has to be at page level?

How well does it handle fetch errors?

Maybe would be good to open a Discussions feature so we can talk outside of the Issues tab.

I'm interested in implementing this library into all my web apps. I was looking into Remix but it isn't stable enough for me as a solo-developer.

btw if this is a serious project I'm also willing to sponsor

[smeijer]

Hi @vasco3,

Sure! I've opened discussions, and converted your issue.

Please understand that this is a library built on top of Nextjs getServersideProps, not a completely new framework like Remix.

That means we have some limitations, like that it has to run on a page level, and that it doesn't work on a component level. But it also comes with the benefit of having Nextjs proven stability.

So yes, I believe next-runtime can be used perfectly fine in production. We handle errors, but you're responsible for showing them to the user.

I made this library for exactly that target audience; solo developers, like myself.

There isn't much complexity to this library, so if it works for your use case, it's likely to keep working. I'm happy to fix any bugs that you come across though.

It is a serious project. I'll keep using it myself. I do offer support and squash bugs. But I don't have the 3 milion USD that Remix got. 😅

[vasco3]

sounds great, thanks for doing this!
I already tried the GET use case, works like a charm. I'll soon try the mutations.

I also watched the talk from Ryan about caching strategy (the one mentioned on the next-runtime docs).
Are you using a CDN to cache data requests in getServersideProps?

[smeijer]

I do. I place my sites behind Cloudflare. But even if you don't, there is still some gain on the browser level.