Strict tsconfig

[fortmarek]

Description

As we are currently releasing the library as untranspiled, we should be as strict as possible in our tsconfig. This PR changes some of the rules to true (especially implicitAny) and fixes any violations of the newly turned on rules.

Reviewers’ hat-rack 🎩

• The CI passing should be enough, you optionally can try running it locally

Screenshots or videos (if needed)

Checklist

• I have added a changelog entry following the Keep a Changelog guidelines.

[naqvitalha]

@fortmarek Right now we're not publishing untranspiled code. I changed it (we discussed this in the morning meeting). Have we really thought enough about this approach for flash-list or other libraries? I'm not sure if it's the best idea for e.g, TS has opinionated configs as well like noImplicitReturns. If someone uses those build will still break.

[fortmarek]

Have we really thought enough about this approach for flash-list or other libraries? I'm not sure if it's the best idea for e.g, TS has opinionated configs as well like noImplicitReturns. If someone uses those build will still break.

Yeah, I forgot we had already changed it. We definitely should default to transpiled build and possibly offer a non-transpiled version if developers would want it. Having stricter tsconfig won't hurt, though.