fix: types incorrectly flag values as potentially null

[aduh95]

AFAICT, every time we call .terminate() or .fingerprint(), we pass an options which cannot be nullish.
The defaultValues also have some always defined values, IMO it makes sense to report them as defined to avoid downstream code to have to use non-null-assertions.

[Acconut]

Sorry, I don't fully understand. Can you share exemplary code and the errors that you are running into?

[aduh95]

Well before this PR, the types are "wrong" (or rather imprecise), e.g. tus.defaultOptions.fingerprint is typed as potentially nullish; after this PR, the types are more "correct", e.g. tus.defaultOptions.fingerprint is typed as not nullish.

[Acconut]

Ok, that makes sense. I get the change for defaultOptions now, thank you. But why are you making the options argument for terminate non-nullish now? It can be null:

tus-js-client/lib/upload.js

Line 118 in 95ca566

static terminate(url, options = {}) {

terminate can also be called by the user without any options. Am I missing something else?

[aduh95]

why are you making the options argument for terminate non-nullish now? It can be null

Maybe this one is wrong, not sure. Let's remove this change.

[Acconut]

Alright, then this looks good, thank you!