You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Investigate if enabling TypeScript's skipLibCheck option helps avoid TypeScript throwing errors when dependencies have issues in the types they provide or their implementation. Ideally we'd want:
not to error if a 3rd party dependency has type issues
error if we misuses or have type issues amongst our own packages (eg. calling code from shared)
Especially:
would we still be confident what we shipped is correctly typed?
which kinds of errors would we open ourselves to in the future?
Why
We've now had several Dependabot PRs stuck because of type issues from 3rd parties, clogging our list of dependency updates over something we don't have control of:
What
Investigate if enabling TypeScript's
skipLibCheck
option helps avoid TypeScript throwing errors when dependencies have issues in the types they provide or their implementation. Ideally we'd want:shared
)Especially:
Why
We've now had several Dependabot PRs stuck because of type issues from 3rd parties, clogging our list of dependency updates over something we don't have control of:
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
skipLibCheck
has on our projectThe text was updated successfully, but these errors were encountered: