text() does not strip UTF-8 BOM from HTTP response

[rhargreaves]

Version: 0.2.4

We have an HTTP backend which adds a UTF-8 BOM to the start of HTTP responses. We noticed that it is present in the string returned by text(). It seems Node's own fetch() method have recently added a fix which strips out BOMs:

node-fetch/node-fetch#1482

Might be worth considering doing something similar? It doesn't feel right that text() returns a string which still contains a BOM. For now, we have made use of https://www.npmjs.com/package/strip-bom to remove the BOM from the string returned by text()

[JakeChampion]

It looks like the change would be on this line:

js-compute-runtime/c-dependencies/js-compute-runtime/js-compute-builtins.cpp

Line 1138 in f36dee2

result.setString(text);

The consume-body algorithm states that we need to run utf8-decode when the type given is text.