Trying to upgrade my types for node on this project https://github.com/intuit/auto/pull/1317

I get this error

It looks like this is something that would need to be added to the library here. I am unsure of how to do this myself

Fixed by #46.

Thank you!

When I connect https url (https://example.com) through http proxy (http://127.0.0.1:1080) or create secure websocket connection (wss://example.com) in NodeJS v15.0.1, the following error occurred:

ERR_INVALID_PROTOCOL TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
    at new NodeError (node:internal/errors:258:15)
    at new ClientRequest (node:_http_client:155:11)
    at request (node:https:313:10)
    at get (node:https:317:15)
    at initAsClient (D:\0\node_modules\ws\lib\websocket.js:538:31)
    at new WebSocket (D:\0\node_modules\ws\lib\websocket.js:72:7)
    ... {
  code: 'ERR_INVALID_PROTOCOL'
}

The above Error is thrown due to agent.protocol !== 'https:'

node:_http_client:154

      if (this.agent && this.agent.protocol)
        expectedProtocol = this.agent.protocol;
      
      ...
      
      if (protocol !== expectedProtocol) {
        throw new ERR_INVALID_PROTOCOL(protocol, expectedProtocol);
  }

Then I inspected that agent.protocol was set in node-agent-base module and found out the following code has mis determined the caller module (http/https) of the agent.

get protocol(): string {
	if (typeof this.explicitProtocol === 'string') {
		return this.explicitProtocol;
	}
	return isSecureEndpoint() ? 'https:' : 'http:';
}


function isSecureEndpoint(): boolean {
	const { stack } = new Error();
	if (typeof stack !== 'string') return false;
	return stack.split('\n').some(l => l.indexOf('(https.js:') !== -1);
}

NodeJS may have changed the error stack representation from https.js:313:10 to node:https:313:10, which breaks the isSecureEndpoint() funciton.

Edit isSecureEndpoint() in node_modules/agent-base/dist/src/index.js by replacing the line

return stack.split('\n').some(l => l.indexOf('(https.js:') !== -1);

with

return stack.split('\n').some(l => l.indexOf('(https.js:') !== -1 || l.indexOf('node:https:') !== -1);

temperorarily solved the ploblem.

similar problems: https://github.com/npm/cli/issues/2003

Thanks!

Type 'HttpsProxyAgent' is not assignable to type 'Agent | ((parsedUrl: URL) => Agent)'.   Property 'maxTotalSockets' is missing in type 'HttpsProxyAgent' but required in type 'Agent'.

• @types/node@~12.19.0 contains http.Agent class with mandatory maxTotalSockets property.
• @types/node-fetch@2.5.7 RequestInit interface uses Agent from Node http.
• https-proxy-agent@5.0.0 uses Agent class from agent-base@6 which has no maxTotalSockets property.

Therefore it's impossible to assign HttpsProxyAgent to the node-fetch's agent.

• Fixed https://github.com/TooTallNate/node-agent-base/issues/48
• Updated node to 12.19.1 last LTS version.
• Added maxTotalSockets property for types compatibility.

Type 'HttpsProxyAgent' is not assignable to type 'Agent | ((parsedUrl: URL) => Agent)'. Property 'maxTotalSockets' is missing in type 'HttpsProxyAgent' but required in type 'Agent'.

• @types/node@~12.19.0 contains http.Agent class with mandatory maxTotalSockets property.
• @types/node-fetch@2.5.7 RequestInit interface uses Agent from Node http.
• https-proxy-agent@5.0.0 uses Agent class from agent-base@6 which has no maxTotalSockets property.

Therefore it's impossible to assign HttpsProxyAgent to the node-fetch's agent.

See https://github.com/TooTallNate/node-https-proxy-agent/issues/114

Thank you!

Description of Change This PR fixes compatibility issues with node 14 typings mentioned in #43 . It should also solved this issue: https://github.com/TooTallNate/node-https-proxy-agent/issues/108

Release Notes

• Updated @types/node to 14.0.20
• Added the missing freeSockets property in a similar way to how the sockets property is handled (declared and initialized for compatibility but not used).

Thanks @a-ursino!

Also ran prettier on the files and ran yarn upgrade to fix security advisory warnings.

So, this module was not working as expected. It works by first calling url.parse() on the given URL. Then it does a DNS resolution on the hostname, and resets the hostname property with the IP address.

Unfortunately, the url.format() function prefers the host property over the hostname property, so setting hostname ends up being a no-op.

For example:

> process.version
'v12.18.4'

> const parsed = url.parse('https://example.com/hi')

// Reset `hostname`
> parsed.hostname = '1.2.3.4'
'1.2.3.4'

// `host` is preferred over `hostname`, so `url.format()` returns original URL
> url.format(parsed)
'https://example.com/hi'

> url.format(parsed) === parsed.href
true

This PR addresses that issue by overwriting both host and hostname appropriately. Ensuring that the proper "Host" request header is set during redirects is also addressed here, with additional tests.

Added.

Nope. Wtf.

I'm not sure, but anyways we should address that in a different PR.

So, this module was not working as expected. It works by first calling url.parse() on the given URL. Then it does a DNS resolution on the hostname, and resets the hostname property with the IP address.

Unfortunately, the url.format() function prefers the host property over the hostname property, so setting hostname ends up being a no-op.

For example:

> process.version
'v12.18.4'

> const parsed = url.parse('https://example.com/hi')

// Reset `hostname`
> parsed.hostname = '1.2.3.4'
'1.2.3.4'

// `host` is preferred over `hostname`, so `url.format()` returns original URL
> url.format(parsed)
'https://example.com/hi'

> url.format(parsed) === parsed.href
true

This PR addresses that issue by overwriting both host and hostname appropriately. Ensuring that the proper "Host" request header is set during redirects is also addressed here, with additional tests.

Bumps node-fetch from 1.7.3 to 2.6.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/bitinn/node-fetch/releases">node-fetch's releases</a>.</em></p> <blockquote> <h2>v2.6.1</h2> <p><strong>This is an important security release. It is strongly recommended to update as soon as possible.</strong></p> <p>See <a href="https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261">CHANGELOG</a> for details.</p> <h2>v2.6.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.6.0/CHANGELOG.md#v260">CHANGELOG</a>.</p> <h2>v2.5.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.5.0/CHANGELOG.md#v250">CHANGELOG</a>.</p> <h2>v2.4.1</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.4.1/CHANGELOG.md#v241">CHANGELOG</a>.</p> <h2>v2.4.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.4.0/CHANGELOG.md#v240">CHANGELOG</a>.</p> <h2>v2.3.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.3.0/CHANGELOG.md#v230">CHANGELOG</a>.</p> <h2>v2.2.1</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.2.1/CHANGELOG.md#v221">CHANGELOG</a>.</p> <h2>Version 2.1.2</h2> <ul> <li>Fix: allow <code>Body</code> methods to work on ArrayBuffer<code>-backed </code>Body` objects</li> <li>Fix: reject promise returned by <code>Body</code> methods when the accumulated <code>Buffer</code> exceeds the maximum size</li> <li>Fix: support custom <code>Host</code> headers with any casing</li> <li>Fix: support importing <code>fetch()</code> from TypeScript in <code>browser.js</code></li> <li>Fix: handle the redirect response body properly</li> </ul> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.1.2/CHANGELOG.md#v212">CHANGELOG</a>.</p> <h2>Version 2.1.1</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.1.1/CHANGELOG.md#v211">CHANGELOG</a>.</p> <p>Fix packaging errors in version 2.1.0.</p> <h2>Version 2.1.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.1.0/CHANGELOG.md#v210">CHANGELOG</a>:</p> <ul> <li>Enhance: allow using ArrayBuffer as the <code>body</code> of a <code>fetch()</code> or <code>Request</code></li> <li>Fix: store HTTP headers of a <code>Headers</code> object internally with the given case, for compatibility with older servers that incorrectly treated header names in a case-sensitive manner</li> <li>Fix: silently ignore invalid HTTP headers</li> <li>Fix: handle HTTP redirect responses without a <code>Location</code> header just like non-redirect responses</li> <li>Fix: include bodies when following a redirection when appropriate</li> </ul> <h2>Version 2.0.0</h2> <p>This is a major release. See <a href="https://github.com/bitinn/node-fetch/blob/master/UPGRADE-GUIDE.md">upgrade guide</a> on how to upgrade from v1.x, and the <a href="https://github.com/bitinn/node-fetch/blob/master/CHANGELOG.md">changelog</a> for all changes.</p> <h2>v2.0.0-alpha.9</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md">node-fetch's changelog</a>.</em></p> <blockquote> <h2>v2.6.1</h2> <p><strong>This is an important security release. It is strongly recommended to update as soon as possible.</strong></p> <ul> <li>Fix: honor the <code>size</code> option after following a redirect.</li> </ul> <h2>v2.6.0</h2> <ul> <li>Enhance: <code>options.agent</code>, it now accepts a function that returns custom http(s).Agent instance based on current URL, see readme for more information.</li> <li>Fix: incorrect <code>Content-Length</code> was returned for stream body in 2.5.0 release; note that <code>node-fetch</code> doesn't calculate content length for stream body.</li> <li>Fix: <code>Response.url</code> should return empty string instead of <code>null</code> by default.</li> </ul> <h2>v2.5.0</h2> <ul> <li>Enhance: <code>Response</code> object now includes <code>redirected</code> property.</li> <li>Enhance: <code>fetch()</code> now accepts third-party <code>Blob</code> implementation as body.</li> <li>Other: disable <code>package-lock.json</code> generation as we never commit them.</li> <li>Other: dev dependency update.</li> <li>Other: readme update.</li> </ul> <h2>v2.4.1</h2> <ul> <li>Fix: <code>Blob</code> import rule for node < 10, as <code>Readable</code> isn't a named export.</li> </ul> <h2>v2.4.0</h2> <ul> <li>Enhance: added <code>Brotli</code> compression support (using node's zlib).</li> <li>Enhance: updated <code>Blob</code> implementation per spec.</li> <li>Fix: set content type automatically for <code>URLSearchParams</code>.</li> <li>Fix: <code>Headers</code> now reject empty header names.</li> <li>Fix: test cases, as node 12+ no longer accepts invalid header response.</li> </ul> <h2>v2.3.0</h2> <ul> <li>Enhance: added <code>AbortSignal</code> support, with README example.</li> <li>Enhance: handle invalid <code>Location</code> header during redirect by rejecting them explicitly with <code>FetchError</code>.</li> <li>Fix: update <code>browser.js</code> to support react-native environment, where <code>self</code> isn't available globally.</li> </ul> <h2>v2.2.1</h2> <ul> <li>Fix: <code>compress</code> flag shouldn't overwrite existing <code>Accept-Encoding</code> header.</li> <li>Fix: multiple <code>import</code> rules, where <code>PassThrough</code> etc. doesn't have a named export when using node <10 and <code>--experimental-modules</code> flag.</li> <li>Other: Better README.</li> </ul> <h2>v2.2.0</h2> <ul> <li>Enhance: Support all <code>ArrayBuffer</code> view types</li> <li>Enhance: Support Web Workers</li> <li>Enhance: Support Node.js' <code>--experimental-modules</code> mode; deprecate <code>.es.js</code> file</li> <li>Fix: Add <code>__esModule</code> property to the exports object</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/node-fetch/node-fetch/commit/b5e2e41b2b50bf2997720d6125accaf0dd68c0ab"><code>b5e2e41</code></a> update version number</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334"><code>2358a6c</code></a> Honor the <code>size</code> option after following a redirect and revert data uri support</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/8c197f8982a238b3c345c64b17bfa92e16b4f7c4"><code>8c197f8</code></a> docs: Fix typos and grammatical errors in README.md (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/686">#686</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/1e99050f944ac435fce26a9549eadcc2419a968a"><code>1e99050</code></a> fix: Change error message thrown with redirect mode set to error (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/653">#653</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/244e6f63d42025465796e3ca4ce813bf2c31fc5b"><code>244e6f6</code></a> docs: Show backers in README</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/6a5d192034a0f438551dffb6d2d8df2c00921d16"><code>6a5d192</code></a> fix: Properly parse meta tag when parameters are reversed (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/682">#682</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/47a24a03eb49a49d81b768892aee10074ed54a91"><code>47a24a0</code></a> chore: Add opencollective badge</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/7b136627c537cb24430b0310638c9177a85acee1"><code>7b13662</code></a> chore: Add funding link</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/5535c2ed478d418969ecfd60c16453462de2a53f"><code>5535c2e</code></a> fix: Check for global.fetch before binding it (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/674">#674</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/1d5778ad0d910dbd1584fb407a186f5a0bc1ea22"><code>1d5778a</code></a> docs: Add Discord badge</li> <li>Additional commits viewable in <a href="https://github.com/bitinn/node-fetch/compare/1.7.3...v2.6.1">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~akepinski">akepinski</a>, a new releaser for node-fetch since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps mixin-deep from 1.3.1 to 1.3.2. <details> <summary>Commits</summary>

• 754f0c2 1.3.2
• 90ee1fa ensure keys are valid when mixing in values
• See full diff in compare view </details> <details> <summary>Maintainer changes</summary>

This version was pushed to npm by doowb, a new releaser for mixin-deep since your current version. </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Sorry for the delay on this. This is a good change. Would you be able to fix the merge conflicts?

Bumps node-fetch from 1.7.3 to 2.6.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/bitinn/node-fetch/releases">node-fetch's releases</a>.</em></p> <blockquote> <h2>v2.6.1</h2> <p><strong>This is an important security release. It is strongly recommended to update as soon as possible.</strong></p> <p>See <a href="https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261">CHANGELOG</a> for details.</p> <h2>v2.6.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.6.0/CHANGELOG.md#v260">CHANGELOG</a>.</p> <h2>v2.5.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.5.0/CHANGELOG.md#v250">CHANGELOG</a>.</p> <h2>v2.4.1</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.4.1/CHANGELOG.md#v241">CHANGELOG</a>.</p> <h2>v2.4.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.4.0/CHANGELOG.md#v240">CHANGELOG</a>.</p> <h2>v2.3.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.3.0/CHANGELOG.md#v230">CHANGELOG</a>.</p> <h2>v2.2.1</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.2.1/CHANGELOG.md#v221">CHANGELOG</a>.</p> <h2>Version 2.1.2</h2> <ul> <li>Fix: allow <code>Body</code> methods to work on ArrayBuffer<code>-backed </code>Body` objects</li> <li>Fix: reject promise returned by <code>Body</code> methods when the accumulated <code>Buffer</code> exceeds the maximum size</li> <li>Fix: support custom <code>Host</code> headers with any casing</li> <li>Fix: support importing <code>fetch()</code> from TypeScript in <code>browser.js</code></li> <li>Fix: handle the redirect response body properly</li> </ul> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.1.2/CHANGELOG.md#v212">CHANGELOG</a>.</p> <h2>Version 2.1.1</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.1.1/CHANGELOG.md#v211">CHANGELOG</a>.</p> <p>Fix packaging errors in version 2.1.0.</p> <h2>Version 2.1.0</h2> <p>See <a href="https://github.com/bitinn/node-fetch/blob/v2.1.0/CHANGELOG.md#v210">CHANGELOG</a>:</p> <ul> <li>Enhance: allow using ArrayBuffer as the <code>body</code> of a <code>fetch()</code> or <code>Request</code></li> <li>Fix: store HTTP headers of a <code>Headers</code> object internally with the given case, for compatibility with older servers that incorrectly treated header names in a case-sensitive manner</li> <li>Fix: silently ignore invalid HTTP headers</li> <li>Fix: handle HTTP redirect responses without a <code>Location</code> header just like non-redirect responses</li> <li>Fix: include bodies when following a redirection when appropriate</li> </ul> <h2>Version 2.0.0</h2> <p>This is a major release. See <a href="https://github.com/bitinn/node-fetch/blob/master/UPGRADE-GUIDE.md">upgrade guide</a> on how to upgrade from v1.x, and the <a href="https://github.com/bitinn/node-fetch/blob/master/CHANGELOG.md">changelog</a> for all changes.</p> <h2>v2.0.0-alpha.9</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md">node-fetch's changelog</a>.</em></p> <blockquote> <h2>v2.6.1</h2> <p><strong>This is an important security release. It is strongly recommended to update as soon as possible.</strong></p> <ul> <li>Fix: honor the <code>size</code> option after following a redirect.</li> </ul> <h2>v2.6.0</h2> <ul> <li>Enhance: <code>options.agent</code>, it now accepts a function that returns custom http(s).Agent instance based on current URL, see readme for more information.</li> <li>Fix: incorrect <code>Content-Length</code> was returned for stream body in 2.5.0 release; note that <code>node-fetch</code> doesn't calculate content length for stream body.</li> <li>Fix: <code>Response.url</code> should return empty string instead of <code>null</code> by default.</li> </ul> <h2>v2.5.0</h2> <ul> <li>Enhance: <code>Response</code> object now includes <code>redirected</code> property.</li> <li>Enhance: <code>fetch()</code> now accepts third-party <code>Blob</code> implementation as body.</li> <li>Other: disable <code>package-lock.json</code> generation as we never commit them.</li> <li>Other: dev dependency update.</li> <li>Other: readme update.</li> </ul> <h2>v2.4.1</h2> <ul> <li>Fix: <code>Blob</code> import rule for node < 10, as <code>Readable</code> isn't a named export.</li> </ul> <h2>v2.4.0</h2> <ul> <li>Enhance: added <code>Brotli</code> compression support (using node's zlib).</li> <li>Enhance: updated <code>Blob</code> implementation per spec.</li> <li>Fix: set content type automatically for <code>URLSearchParams</code>.</li> <li>Fix: <code>Headers</code> now reject empty header names.</li> <li>Fix: test cases, as node 12+ no longer accepts invalid header response.</li> </ul> <h2>v2.3.0</h2> <ul> <li>Enhance: added <code>AbortSignal</code> support, with README example.</li> <li>Enhance: handle invalid <code>Location</code> header during redirect by rejecting them explicitly with <code>FetchError</code>.</li> <li>Fix: update <code>browser.js</code> to support react-native environment, where <code>self</code> isn't available globally.</li> </ul> <h2>v2.2.1</h2> <ul> <li>Fix: <code>compress</code> flag shouldn't overwrite existing <code>Accept-Encoding</code> header.</li> <li>Fix: multiple <code>import</code> rules, where <code>PassThrough</code> etc. doesn't have a named export when using node <10 and <code>--experimental-modules</code> flag.</li> <li>Other: Better README.</li> </ul> <h2>v2.2.0</h2> <ul> <li>Enhance: Support all <code>ArrayBuffer</code> view types</li> <li>Enhance: Support Web Workers</li> <li>Enhance: Support Node.js' <code>--experimental-modules</code> mode; deprecate <code>.es.js</code> file</li> <li>Fix: Add <code>__esModule</code> property to the exports object</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/node-fetch/node-fetch/commit/b5e2e41b2b50bf2997720d6125accaf0dd68c0ab"><code>b5e2e41</code></a> update version number</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334"><code>2358a6c</code></a> Honor the <code>size</code> option after following a redirect and revert data uri support</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/8c197f8982a238b3c345c64b17bfa92e16b4f7c4"><code>8c197f8</code></a> docs: Fix typos and grammatical errors in README.md (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/686">#686</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/1e99050f944ac435fce26a9549eadcc2419a968a"><code>1e99050</code></a> fix: Change error message thrown with redirect mode set to error (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/653">#653</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/244e6f63d42025465796e3ca4ce813bf2c31fc5b"><code>244e6f6</code></a> docs: Show backers in README</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/6a5d192034a0f438551dffb6d2d8df2c00921d16"><code>6a5d192</code></a> fix: Properly parse meta tag when parameters are reversed (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/682">#682</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/47a24a03eb49a49d81b768892aee10074ed54a91"><code>47a24a0</code></a> chore: Add opencollective badge</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/7b136627c537cb24430b0310638c9177a85acee1"><code>7b13662</code></a> chore: Add funding link</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/5535c2ed478d418969ecfd60c16453462de2a53f"><code>5535c2e</code></a> fix: Check for global.fetch before binding it (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/674">#674</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/1d5778ad0d910dbd1584fb407a186f5a0bc1ea22"><code>1d5778a</code></a> docs: Add Discord badge</li> <li>Additional commits viewable in <a href="https://github.com/bitinn/node-fetch/compare/1.7.3...v2.6.1">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~akepinski">akepinski</a>, a new releaser for node-fetch since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>