Remix loader private-only flag to prevent client serialization
When developing a Remix route, I want to guarantee that data fetched in a loader never becomes part of the client‑side hydration payload, even if the loader returns a large object that contains fields meant to stay server‑only. The framework currently serializes every loader return value to JSON, and there is no declarative way to mark a loader as “private‑o
remix