Large bundle size

[osdiab]

When using my fork or io-ts-reporters which is just tracking master, the bundle size is much larger than it ought to be. This showed up on the project I am using it on.

https://bundlephobia.com/result?p=@osdiab/[email protected]

This library can potentially make use of tree shaking or something to avoid bundling the entirety of io-ts and fp-ts with it. Maybe:

• sideEffects: false in package.json
• ESModules as an output option
• maybe a bundler like Rollup can help
• would having those as peer dependencies be a good idea?

[gillchristian]

We should definitely look into that. Probably we could implement all of your suggestions and get some good results.

https://bundlephobia.com/[email protected]

[gillchristian]

@osdiab I updated your comment making it a checklist and and marked some as done as per #34

UPDATE: it seems like that alone made a huge difference

• v1.1.0: 75.5kB Minified / 16.1kB Minified + Gzipped

• v1.2.0: 2.4kB Minified / 923B Minified + Gzipped

[osdiab]

@OliverJAsh I saw your issue here: gcanti/fp-ts#1044

It seems all the imports in this library are also /lib/* imports when /es6/* imports would also allow tree shaking of those libraries (as of now this library still pulls in a lot of data when analyzing my bundle size on the side of my app). Perhaps we can emulate how gcanti achieves the separate es6 and lib bundles here too

[osdiab]

This was recently merged into fp-ts: gcanti/fp-ts#1241

[osdiab]

just realized as well that this uses a lot of fp-ts utilities - with just io-ts it only uses fp-ts/Either and fp-ts/pipeable which results in about 10kb from that library before compression, but with io-ts-reporters I'm getting about 50kb extra from all the fp-ts stuff this uses - surprising to me!