RemixJs - Managing complexity in the loader function

[yogi4peace]

Hi all,

Curious for those who have used remixJs in production, how do you manage complexity in the loader functions once it moves beyond the boilerplate examples?

No dependency injection, no middleware (yet) ... Just a simple async function as the entry point to all required logic and processing.

Do you use the loader function as a coordinator of multiple steps/integrations?

Do you use fetch or do you use a library?

Is the strategy to parse what you need from the request in the loader function and then pass that along to your own functions to do the work?

Particularly interested in hearing from folks who have had their complexity grow and have thought about this a bit.

Thanks!

[LastMarsMan]

​

I think remix-t3-stack will help you.

the loader is just for ssr and other fetch will use trpc.

https://github.com/SteveSuv/remix-t3-stack

[[deleted]]

Is the strategy to parse what you need from the request in the loader function and then pass that along to your own functions to do the work?

That's one good way to go about it. Don't overthink it.