Last working version is 1.9.0
This broke a number of our nightly CI builds for packages that were depending on io-ts indirectly through a released package. We never imported from fp-ts, and therefore did not list it as a dependency. It seems to me like a change that requires all downstream consumers to make an update to their package.json in order to continue building should be considered non-passive and warrant a major version bump.
Same thing happened to us
Check https://github.com/gcanti/io-ts#installation It works for me.
We never imported from fp-ts, and therefore did not list it as a dependency. It seems to me like a change that requires all downstream consumers to make an update to their package.json in order to continue building should be considered non-passive
@RHolland13 I agree, I'll revert that change.
Patch released https://github.com/gcanti/io-ts/releases/tag/1.10.2
Thanks for fixing this @gcanti.
We are ok with this change if you reintroduce it in a major version.
Most helpful comment
@RHolland13 I agree, I'll revert that change.