Timothy Gu
Timothy Gu
> That would decrease the hypothetical bundle size of node-fetch That would be an edge case, since few people bundle modules intended for Node.js usage. > even if the on-disk...
Hi, thanks for starting this. As a start, I'd say don't bother with some of the changes, like those to the license (`LICENSE.txt`), ESLint (`.eslint*`), Travis CI (`.travis.yml`), and Git...
Thanks for doing the additional investigation! > There should now be support for streams as well. I have had to stop relying on the `decode` function defined in `whatwg-encoding.js` because...
> How soon should we expect the initial worker implementation in #58 to land? First of all, remember we are all volunteers here. Nobody that I know of is paying...
@tbranyen How about https://discord.gg/QhR4JyZ?
As I commented on the crbug, there’s a lot of history in this. See https://github.com/whatwg/url/commit/dc9d83106cada9af507bf37dee3973de97b020fd and the linked tickets. For this PR, you might want to dedupe the tests against...
Looks like all three browsers have implemented this change! ```js a = new URL('http://a/'); assert_equals(Object.prototype.toString.call(a), "[object URL]"); delete URL.prototype[Symbol.toStringTag]; assert_equals(Object.prototype.toString.call(a), "[object Object]"); ```
@alexeyraspopov, no, and https://twitter.com/slicknet/status/782274190451671040.
Or, we can just make the function no-op and `return Promise.resolve();`, which seems sensible.
It should be added. Can you provide a self-contained test case that shows the bug (i.e., not using google.com which is undebuggable)?