@tsapeta@expo Yeah for sure, Expo Modules have been around since long before Nitro. I was mostly curious why you'd keep them separate now, given Nitro's performance, but Kolibri is impressive! Ecosystem compatibility makes sense, thanks for the answer!
@pilcrowonpaper Rate limiting's main use case is protecting endpoints that require authentication. Other endpoints might use IP-based approach. You could also generate a fingerprint on the client with obfuscated rules but it's still workaround-able
.@tan_stack Start: how do you prevent route's `beforeLoad` / `loader` from being run server-side? Unfortunately, the current auth setup requires all network calls to happen in the browser
I've tried `spa.enabled: true` in Vite config and `ssr: false` in route
cc @tannerlinsley