Typia on the Frontend

[karesztrk]

Hey guys, I'm about to start using Typia on my Front-end application. I've successfully set it up, and it works on a single use case with the Rspack plugin.
Now, as far as I can see - from the GitHub discussions - Typia is mainly used on the Backend/Server.

Is there any reason not to use it on a Front-end (ESM)?
I also saw that Typia won't be ESM first in this issue which is odd but reasonable.

[jboyesreach00]

I'm using it on frontend to validate data coming from out-of-repo sources that are not checkable statically. When the data to be validated comes form a 3rd-party with an @types/ package published, Typia is much nicer than recreating the 3rd-party's types in something like Zod.

[karesztrk]

I have settled on Valibot afterall

[samchon]

typia can be used in frontend applications. The important boundary is build-time transformation, not whether the final bundle runs in a browser.

A frontend setup is fine when every typia.*<T>() call is transformed before it reaches the browser bundle, for example through ttsc/ttsx, @typia/unplugin, or typia generate. Do not rely on the transformer running in the browser at runtime; the generated validator code is what should be bundled. For frontend use, keep typia at data boundaries such as API responses, storage payloads, and third-party inputs, and watch bundle size the same way you would for any generated validator code.

Since the original author settled on another validator and there is no typia-side action left here, closing as answered.