Focused crawls are collections of frequently-updated webcrawl data from narrow (as opposed to broad or wide) web crawls, often focused on a single domain or subdomain.
A bit of context, we introduced swr two weeks ago to our codebase. Everything is working fine, but we started to get some reports about some parts of the app being broken in slightly older browsers (Chrome 49, Firefox 59, Edge 18, etc…)
We found out that swr was causing a syntax error in these browsers because webpack by default picked the ESM build (rightly so) but because it's not transp
I've read many similar closed issues, but haven't found a good documented solution on what can I do as a consumer of ky package if I need to support e.g iOS 10.0 browser (that breaks on async/await support currently).
I agree that it's not related to ky itself, but can be a nice help for the consumers of the package.
In our particular can we don't use babel (we use typescript), so I'm
node-fetch currently completely ignoring Content-Length header while consuming response.
Fetch specification about handling Content-Length on server response says almost nothing: https://fetch.spec.whatwg.org/#concept-http-network-fetch (see whatwg/fetch#67)
On other hand, we have a fetch-node specific extension to limit the size of the response.
Presumably these should result in a network error. The current specification doesn't state anything and it's not tested either.
See the README for instructions on where to add tests. In the specification the "blob" case of https://fetch.spec.whatwg.org/#scheme-fetch needs updating to handle current URL’s blob URL entry being null.
A bit of context, we introduced
swrtwo weeks ago to our codebase. Everything is working fine, but we started to get some reports about some parts of the app being broken in slightly older browsers (Chrome 49, Firefox 59, Edge 18, etc…)We found out that
swrwas causing a syntax error in these browsers because webpack by default picked the ESM build (rightly so) but because it's not transp