Feature Request: import only Effect's schema modules #232

json-schema.js imports effect whole whenever it is installed, at the top level, though the converter uses only Schema and JSONSchema. Importing effect/Schema, plus effect/JSONSchema on Effect 3, would load and bundle much less. Both exist from 3.14.2, the lowest version the peer range allows. Effect 4 has only effect/Schema, which is all the conversion in #231 needs. We measured each import on Node 26, and bundled it with rolldown, unminified:

Every command pays the load time, --help included, and a bundled CLI, as ours is, carries the whole package.

Going further, trpc-cli could import no schema library at all. It already falls back to a schema's own ~standard.jsonSchema, and taking the other converters from the user, as oRPC does, would leave nothing to import. CLIs that don't use Effect would save the remaining 120 ms and 1 MB. Users of Valibot, Effect, Zod 3 and zod/mini would pass a converter to createCli, which the help text could suggest as it now suggests installing @valibot/to-json-schema, so it would be a small change for a major release.

Module mode could follow the same rule. Node loads it only when it is used, but since createCli chooses it by its arguments, bundlers include it anyway: with rolldown, a CLI built on a router bundles 612 KB of trpc-cli, 453 KB of it module mode with TypeBox. An entry point of its own, as TypeBox schemas have in trpc-cli/typebox, would leave it out, and give createCli one signature rather than one whose results turn async by its arguments.