Implicit any breaks builds

[eseliger]

Implicit any breaks builds

[felixfbecker]

This blocks our adoption of v1

[Kukkimonsuta]

Workaround: set skipLibCheck in your tsconfig to ignore errors caused by library typings

[BrianMikinski]

@Kukkimonsuta is it desirable for y'all enable strict null checking? If so I'd be interested in contributing. Would it merely be a case of adding the correct typings to the errors the compiler throws and insuring all tests pass or is there more to it?

[Kukkimonsuta]

strictNullChecks have quite slow adoption from my experience, but I'd personally welcome it. To implement it correctly though, you need to have thorough knowledge of the code since you need to specify where null is valid and where not (compiler will help with things used internally, but public api may be more difficult to guess).

On the other hand noImplicitAny should be definitely enabled everywhere (at least in public api specified in typings).

Edit: it seems that noImplicitAny was already resolved: 1a6cdfc 👍

[christopherthielen]

5.0.6 should also be strictNullChecks compliant.

Closing because I think this is solved now, but reopen if necessary