To my knowledge, these types fail to decode correctly in NodeJS version 11.0 and higher:
ObjectDescriptor
UTF8String
NumericString
PrintableString
TeletexString
VideotexString
IA5String
UTCTime
GeneralizedTime
GraphicString
VisibleString
GeneralString
BMPString
The problem starts with this piece of recurring code:
if (typeof TextEncoder !== "undefined") { // Browser JavaScript
dateString = (new TextDecoder("utf-8")).decode(<ArrayBuffer>this.value.subarray(0).buffer);
} else if (typeof Buffer !== "undefined") { // NodeJS
dateString = (new Buffer(this.value)).toString("utf-8");
}
Before NodeJS version 11.0, TextEncoder and TextDecoder were in the util part of the standard library. I did not know about this. I thought they were undefined in NodeJS altogether, so I wrote the above code to accommodate both browser and NodeJS versions. In version 11.0 of NodeJS, both TextEncoder and TextDecoder were made global, which made the first block execute instead of the second. This works fine in a web browser, but in NodeJS, it seems that this.value tends to be a slice of the underlying ArrayBuffer rather than a brand new Uint8Array, so when this.value.subarray(0) is called in NodeJS, it returns the entire underlying ArrayBuffer instead of the slice, which we are expecting to be a copy of this.value.
To my knowledge, these types fail to decode correctly in NodeJS version 11.0 and higher:
ObjectDescriptorUTF8StringNumericStringPrintableStringTeletexStringVideotexStringIA5StringUTCTimeGeneralizedTimeGraphicStringVisibleStringGeneralStringBMPStringThe problem starts with this piece of recurring code:
Before NodeJS version 11.0,
TextEncoderandTextDecoderwere in theutilpart of the standard library. I did not know about this. I thought they were undefined in NodeJS altogether, so I wrote the above code to accommodate both browser and NodeJS versions. In version 11.0 of NodeJS, bothTextEncoderandTextDecoderwere made global, which made the first block execute instead of the second. This works fine in a web browser, but in NodeJS, it seems thatthis.valuetends to be a slice of the underlyingArrayBufferrather than a brand newUint8Array, so whenthis.value.subarray(0)is called in NodeJS, it returns the entire underlyingArrayBufferinstead of the slice, which we are expecting to be a copy ofthis.value.