Jimb Esser

> Hi @Jimbly any plan to merge this ? I'm not the one who can merge to this repository, that would be a question for the maintainers of `node-http-proxy`. Since...

We started getting daily spam too, which is especially bad since it gets forwarded to our Discord channel as well, and GitReports makes it looks like it's coming from me...

This is also something we'd be interested in. When changing some other parts of our pipeline from objects to arrays we got about a 65% reduction in time when loading...

Well, after spending 3 hours debugging a build pipeline issue, only to find that the root cause was a bug I had debugged and tracked down years ago, I've implemented...

I've re-encoded http-parser-js/package.json in UTF8, and published http-parser-js to NPM, please let me know if it fixes the issue for you.

I *think* that package.json is supposed to be UTF8 encoded, however one could argue that NPM parses it without complaints, you may want your system to be able to parse...

@paulbjensen Your issue sounds unrelated to this bug (other than that it's happening with the same module), perhaps open a new bug on the appropriate project and it can be...

Ah, sorry, didn't see you already did over at https://github.com/creationix/http-parser-js/issues/41 ; will continue discussion there.

http-parser-js was never a dependency of flow. The issue, as I understood it, was that flow parses a project's dependencies, and was failing to parse a package.json that NPM had...

Yeah, I think it was saved with ASCII encoding (Notepad will view it fine ; ), instead of UTF8, so has bytes that are not valid when interpreted as UTF8.