Remix v2 Performance, Streaming, Caching, Server/Client Split Remix v2 has no built-in image optimizer and no opaque framework cache — it pushes everything to the standard HTTP layer. The performance surface is four pillars: streaming ( / ), HTTP caching ( export), prefetching ( and ), and a hard server/client split ( / file conventions). Quick Reference export with SWR (forward loader headers to the document) : for server-only modules — build fails loud if the file leaks into the client graph: for slow secondary data : Streaming with and Every promise passed to must be created before any in…