Effect v4 HttpApi Bundle Size Implications on Frontend
Hey team, could someone please shed some light on the bundle size implications in Effect v4 when using HttpApi on the frontend?
Specifically:
If I define my full API schema with HttpApi.make() (or HttpApiBuilder) and then consume it on the client using AtomHttpApi (for end-to-end type safety), will the resulting client-side code pull in:
• Node/platform-specific modules (e.g. from @effect/platform-node or similar)?
• Other server-oriented dependencies or code paths?
… and therefore cause a significant increase in frontend bundle size?
Or is everything nicely tree-shakeable / split so that only the pure client-safe parts (schema + AtomHttpApi runtime) end up in the browser bundle?
Thanks a lot for any insights / measurements / best practices here
Specifically:
If I define my full API schema with HttpApi.make() (or HttpApiBuilder) and then consume it on the client using AtomHttpApi (for end-to-end type safety), will the resulting client-side code pull in:
• Node/platform-specific modules (e.g. from @effect/platform-node or similar)?
• Other server-oriented dependencies or code paths?
… and therefore cause a significant increase in frontend bundle size?
Or is everything nicely tree-shakeable / split so that only the pure client-safe parts (schema + AtomHttpApi runtime) end up in the browser bundle?
Thanks a lot for any insights / measurements / best practices here
Similar Threads
Was this page helpful?
