Add fatal flag to TextDecoder to fix inconsistency

[etodanik]

The purpose of this PR is:

Fix inconsistency between fetch-blob and the browser File behavior.
#118

This is what had to change:

Make invalid utf-8 decoding non fatal

[jimmywarting]

the default value is false. so is this really necessary?

[etodanik]

Yes , it didn't work for me without it.

[jimmywarting]

weird, is there some node version you are using that throws an error and use fatal=true?

i tried node 16 and executed new TextDecoder().decode(Uint8Array.from([_issue_118_])) and i did not get any error.

[etodanik]

Not node, specifically the polyfill that Next.js uses (and next.js is quite widespread. Enough to set an explicit default IMHO)

[jimmywarting]

Not node, specifically the polyfill that Next.js uses

Oh, well... that ain't good. I would like to follow up on the polyfill that next.js uses and report to them that they have a buggy implementation of TextDecoder

[jimmywarting]

Going to close this b/c there is something wrong on Next.js part - not ours
The pressure should be on them to fix it.

What you could do is freaze the global TextDecoder so it can't be overwritten when there is already something working without a polyfill