Reduce library size [Question] [Enhancement]

At first — thank you for this awesome project.

Recently I debug my bundle and recognise that zod is almost the same as react-dom library and it’s 114kb non gziped code. I use latest version of zod 3.1.0.

Used named import of all zod, but also tried something like import { string } from 'zod' with the same result

import { z } from 'zod';

export const linkShema = z.object({
  title: z.string(),
  link: z.string(),
});

Is it possible to remove at least unused parts of code from my bundle, because 100+ kb it’s a lot.

[colinhacks]

Like @scotttrinh said, there’s a lot of circular dependencies where the base class is dependent on its own subclasses. This is necessary to add convenience methods like .and, .or, .array, etc. So Zod is structurally incompatible with treesplitting to some extent.

I added minification to the Rollup config which seems to have decreased the size of index.mjs by 50kb (50% reduction).

[scotttrinh]

More manageable when gzipped and/or minified:

$ npx -p gzip-size-cli gzip-size index.mjs --include-original
108 kB → 17.5 kB
$ npx -p js-size js-size index.mjs
┌─────────────────┬─────────┐
│ Original (gzip) │ 17.5 kB │
├─────────────────┼─────────┤
│ Minified (gzip) │ 10.3 kB │
├─────────────────┼─────────┤
│ Difference      │ 7.19 kB │
├─────────────────┼─────────┤
│ Percent         │ 58.94%  │
└─────────────────┴─────────┘

looking at the output, I’m not sure what else we could do: it’s pretty much just the output of tsc here. I don’t think it’s common practice for TypeScript libraries to do any minifying or anything, so I think this ends up falling on you as a consumer to minimize the impact of the library on your bundle. As it is, there is little that can be shaken out of zod, I think, since most of the “weight” is in the parser which is the part that does all of the real work. I’m no tree-shaking expert, though, so if anyone else can weigh in (no pun intended), I’d be interested to hear a more experienced take on this!