v4.0.8

What's Changed

• fix: no Brotli decompression on an empty HEAD response by @barjin in #150

Full Changelog: v4.0.7...v4.0.8

v4.0.7

What's Changed

• fix: consistent proxy auth handling by @barjin in #146

Full Changelog: v4.0.6...v4.0.7

v4.0.6

What's Changed

• feat: log CONNECT error response body by @barjin in #139

Full Changelog: v4.0.5...v4.0.6

v4.0.5

What's Changed

• fix: process http over https proxy correctly by @barjin in #129

Full Changelog: v4.0.4...v4.0.5

v4.0.4

What's Changed

• fix: pass the timeout to the resolveProtocol calls by @barjin in #131

Full Changelog: v4.0.3...v4.0.4

v4.0.3

What's Changed

• fix: correct types for got scraping by @vladfrangu in #122

Full Changelog: v4.0.2...v4.0.3

v4.0.2

What's Changed

• fix: compile to es2021 to properly support node 16.x by @vladfrangu in #120

Full Changelog: v4.0.1...v4.0.2

v4.0.1

What's Changed

• fix: compile module in one file and add missing ignores by @vladfrangu in #117

Full Changelog: v4.0.0...v4.0.1

v4.0.0

The module is now ESM only

This means you have to import it by using an import expression, or the import() method. You can do so by either migrating your project to ESM, or importing got-scraping in an async context

-const { gotScraping } = require('got-scraping');
+import { gotScraping } from 'got-scraping';

If you cannot migrate to ESM, here's an example of how to import it in an async context:

let gotScraping;

async function fetchWithGotScraping(url) {
    gotScraping ??= (await import('got-scraping')).gotScraping;

    return gotScraping.get(url);
}

What's Changed

• feat: add export of hooks and TransformHeadersAgent by @foxt451 in #102
• feat: ESM migration of got-scraping by @vladfrangu in #109
• feat: add Cloudflare blocking benchmarking by @barjin in #114

New Contributors

• @foxt451 made their first contribution in #102

Full Changelog: v3.2.15...v4.0.0

v3.2.15

What's Changed

• fix: proxies work correctly in Node v18.17 by @barjin in #98

Full Changelog: v3.2.13...v3.2.15