profile
viewpoint
Nathan Rajlich TooTallNate @vercel San Francisco, CA https://n8.io Programmer / Nerd. Former @nodejs core committer. Revolutionizing deployments @vercel. Before you ask, I'm 6’6”

kelektiv/node.bcrypt.js 5547

bcrypt for NodeJs

nodejs/nan 2835

Native Abstractions for Node.js

chjj/pty.js 811

Bindings to forkpty(3) for node.js.

TooTallNate/ansi-canvas 550

Render a <canvas> node to your terminal

leo/args 394

Toolkit for building command line interfaces

TooTallNate/ansi.js 309

Advanced ANSI formatting tool for Node.js

importpw/import 294

`import` is a simple and fast module system for Bash and other Unix shells

substack/node-ent 208

Encode and decode HTML entities

gf3/IRC-js 173

The best IRC library for node.js

stephenmathieson/node-tlds 99

list of TLDs

starteddbusjs/node-dbus-next

started time in 4 days

release TooTallNate/node-agent-base

6.0.2

released time in 4 days

created tagTooTallNate/node-agent-base

tag6.0.2

Turn a function into an `http.Agent` instance

created time in 4 days

push eventTooTallNate/node-agent-base

Nathan Rajlich

commit sha c4b8ea2e1a11bae023bb09b708050a50418204e9

6.0.2

view details

push time in 4 days

push eventTooTallNate/node-agent-base

Nathan Rajlich

commit sha 4d40e6e4ef245ce2c1855ec4550cfb32acc7d2b7

Fix SOCKS in readme

view details

push time in 4 days

issue closedTooTallNate/node-agent-base

Doesn't work with @types/node@14

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

I get this error

Screen Shot 2020-07-01 at 9 18 37 AM

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

Screen Shot 2020-07-01 at 9 19 20 AM

closed time in 4 days

hipstersmoothie

issue commentTooTallNate/node-agent-base

Doesn't work with @types/node@14

Fixed by #46.

hipstersmoothie

comment created time in 4 days

push eventTooTallNate/node-agent-base

Nathan Rajlich

commit sha 5f619ad2bfbe906d023dd105e97aaed659ec2d24

Test Node 15 (#50)

view details

push time in 4 days

delete branch TooTallNate/node-agent-base

delete branch : test/node-15

delete time in 4 days

push eventTooTallNate/node-agent-base

沈鸿飞

commit sha 8e45696eea1b099d68795e54a9793987d5749b98

fix ERR_INVALID_PROTOCOL caused by agent.protocol (#47) (NodeJS 15 changed new Error().stack representation)

view details

push time in 4 days

PR merged TooTallNate/node-agent-base

fix ERR_INVALID_PROTOCOL in NodeJS 15 when connect https url through http proxy

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

+1 -1

0 comment

1 changed file

ShenHongFei

pr closed time in 4 days

push eventTooTallNate/node-agent-base

Nathan Rajlich

commit sha b58cf4bd391de49cf234bdad9c5f54a5d9ec9253

Remove extra `maxTotalSockets`

view details

push time in 4 days

push eventTooTallNate/node-agent-base

Viacheslav Dobromyslov

commit sha 43b5ad5a62baae8f777223cc92fd31a6b8c77e11

Fixed https://github.com/TooTallNate/node-https-proxy-agent/issues/114 (#49) Added maxTotalSockets property for types compatibility.

view details

push time in 4 days

issue closedTooTallNate/node-https-proxy-agent

Property 'maxTotalSockets' is missing in type 'HttpsProxyAgent'

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.

closed time in 4 days

dobromyslov

PR merged TooTallNate/node-agent-base

Fixed https://github.com/TooTallNate/node-agent-base/issues/48
  • 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.
+2 -0

0 comment

1 changed file

dobromyslov

pr closed time in 4 days

issue closedTooTallNate/node-agent-base

Node@12 Property 'maxTotalSockets' is missing in type 'HttpsProxyAgent'

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

closed time in 4 days

dobromyslov

push eventdobromyslov/node-agent-base

Damien Bénard

commit sha f57e2e75a440bbe90d28f649134641310b443c18

Fixed compatibility with node 14 typings (#46) Co-authored-by: Damien Bénard <damien.benard@amplexor.com>

view details

Nathan Rajlich

commit sha 95f99dd5f47f7ce3a6bfbcd11ec00679f26b62cd

Add `maxTotalSockets` :/

view details

Nathan Rajlich

commit sha e9da7bae515997b80b27c43f42ad93993c23aa30

Merge branch 'master' into master

view details

push time in 4 days

push eventTooTallNate/node-agent-base

Nathan Rajlich

commit sha 95f99dd5f47f7ce3a6bfbcd11ec00679f26b62cd

Add `maxTotalSockets` :/

view details

Nathan Rajlich

commit sha 98f1b1be8d197d07438b38895e09be0ecf11fd56

Merge branch 'master' of github.com:TooTallNate/node-agent-base into test/node-15

view details

push time in 4 days

push eventTooTallNate/node-agent-base

Nathan Rajlich

commit sha 95f99dd5f47f7ce3a6bfbcd11ec00679f26b62cd

Add `maxTotalSockets` :/

view details

push time in 4 days

push eventTooTallNate/node-agent-base

Damien Bénard

commit sha f57e2e75a440bbe90d28f649134641310b443c18

Fixed compatibility with node 14 typings (#46) Co-authored-by: Damien Bénard <damien.benard@amplexor.com>

view details

Nathan Rajlich

commit sha a87d278a04a1c13f9ce3d126b099f493e8df7205

Merge branch 'master' of github.com:TooTallNate/node-agent-base into test/node-15

view details

push time in 4 days

create barnchTooTallNate/node-agent-base

branch : test/node-15

created branch time in 4 days

PR opened TooTallNate/node-agent-base

Test Node 15
+1 -1

0 comment

1 changed file

pr created time in 4 days

pull request commentTooTallNate/node-agent-base

fix: compatibility with node 14 typings

Thank you!

dabenard

comment created time in 4 days

push eventTooTallNate/node-agent-base

Damien Bénard

commit sha f57e2e75a440bbe90d28f649134641310b443c18

Fixed compatibility with node 14 typings (#46) Co-authored-by: Damien Bénard <damien.benard@amplexor.com>

view details

push time in 4 days

PR merged TooTallNate/node-agent-base

fix: compatibility with node 14 typings

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).
+5 -1

1 comment

2 changed files

dabenard

pr closed time in 4 days

pull request commentvercel/fetch-retry

Don’t retry if the request was aborted

Thanks @a-ursino!

a-ursino

comment created time in 8 days

push eventvercel/fetch-retry

Alessandro Ursino

commit sha 2128929a99d65837bb180c417fe110e2d7d501f8

Don’t retry if the request was aborted (#32)

view details

push time in 8 days

push eventTooTallNate/node-pac-resolver

Nathan Rajlich

commit sha 0793312139c7f210be409218fdc4bf814dc731cf

README++

view details

push time in 11 days

release vercel/fetch

6.1.0

released time in 11 days

created tagvercel/fetch

tag6.1.0

Opinionated `fetch` (with retrying and DNS caching) optimized for use inside microservices

created time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha f7aa179ecb8eb2f70e459555dec6fb8746f86486

6.1.0

view details

push time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha 0bd58706cc4fbf8ff5c08e14e1f320ec06487dde

Rename to `@vercel/fetch` (#50) * Rename to `@vercel/fetch` * Run `yarn upgrade` * Use `@vercel/fetch-retry` * Use `@vercel/fetch-cached-dns` * Update `@vercel/fetch-cached-dns` to v2.0.1

view details

push time in 11 days

delete branch vercel/fetch

delete branch : rename/vercel

delete time in 11 days

PR merged vercel/fetch

Reviewers
Rename to `@vercel/fetch`

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

+594 -375

0 comment

6 changed files

TooTallNate

pr closed time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha 516c1c6aa6a576fa416d39ed1d65ea24e46a5b93

Use GH Actions instead of CircleCI (#51) * Use GH Actions instead of CircleCI * Fix test on Node 8 * Disable eslint "linebreak-style" for Windows * Add GH Actions badge to readme

view details

Nathan Rajlich

commit sha 9eb0d2e22280aa583d24247048c25ebf4eeda2a7

Merge remote-tracking branch 'origin' into rename/vercel

view details

push time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha 516c1c6aa6a576fa416d39ed1d65ea24e46a5b93

Use GH Actions instead of CircleCI (#51) * Use GH Actions instead of CircleCI * Fix test on Node 8 * Disable eslint "linebreak-style" for Windows * Add GH Actions badge to readme

view details

push time in 11 days

delete branch vercel/fetch

delete branch : add/gh-actions

delete time in 11 days

PR merged vercel/fetch

Use GH Actions instead of CircleCI
+52 -43

0 comment

5 changed files

TooTallNate

pr closed time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha 55b72b5281be97bf6c6a522694814ef101a1fa71

Add GH Actions badge to readme

view details

push time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha ba58c48489b82f9e93655f58a779e9636896c8a4

Disable eslint "linebreak-style" for Windows

view details

push time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha 9ced34094a58a41cc34094002f6a2e93bee78306

Fix test on Node 8

view details

push time in 11 days

PR opened vercel/fetch

Use GH Actions instead of CircleCI
+46 -40

0 comment

2 changed files

pr created time in 11 days

create barnchvercel/fetch

branch : add/gh-actions

created branch time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha a24e90318f9f355359e0c431a84b82c32fec09e5

Update `@vercel/fetch-cached-dns` to v2.0.1

view details

push time in 11 days

release vercel/fetch-cached-dns

2.0.1

released time in 11 days

created tagvercel/fetch-cached-dns

tag2.0.1

A decorator on top of `fetch` that caches the DNS query

created time in 11 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha 9e459541c617ea7316c47a6fb9f9e1221036e84b

Include `util.js` in npm package

view details

Nathan Rajlich

commit sha 0e278d56fc01f65e83542a9609eadf4ac717bc04

2.0.1

view details

push time in 11 days

push eventvercel/fetch

Nathan Rajlich

commit sha 37ccbeeef6f25b655da662c94281ed7f5e41b2de

Use `@vercel/fetch-cached-dns`

view details

push time in 11 days

release vercel/fetch-cached-dns

2.0.0

released time in 11 days

created tagvercel/fetch-cached-dns

tag2.0.0

A decorator on top of `fetch` that caches the DNS query

created time in 11 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha bae043bef232db91e8743aea4b37ef7c0bae2c1c

2.0.0

view details

push time in 11 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha c1b741d64fa5c041750f6095c7571e393b81aef4

Properly set the IP address in the request URL (#27) * Properly set the IP address in the request URL 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. * Fix typo. Thanks @styfle Co-authored-by: Steven <steven@ceriously.com> * Remove `dns` * Test `body.url` too * Remove `dns` again :/ * Restore `res.url` back to contain the hostname instead of IP Co-authored-by: Steven <steven@ceriously.com>

view details

push time in 11 days

delete branch vercel/fetch-cached-dns

delete branch : fix

delete time in 11 days

PR merged vercel/fetch-cached-dns

Reviewers
Properly set the IP address in the request URL

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.

+97 -46

0 comment

3 changed files

TooTallNate

pr closed time in 11 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha 511f970cdbcc72458f7168e3bb7a75255c13bdbc

Restore `res.url` back to contain the hostname instead of IP

view details

push time in 11 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha cf1064d4fe66f1a9c992d3172b69dc3defe08803

Remove `dns` again :/

view details

push time in 11 days

PullRequestReviewEvent

Pull request review commentvercel/fetch-cached-dns

Properly set the IP address in the request URL

 /* eslint-env jest*/+const dns = require('dns') const listen = require('async-listen') const { createServer } = require('http') const cachedDNSFetch = require('./index')(require('node-fetch')) +dns.setServers(['8.8.8.8', '1.1.1.1'])+ /**  * Using `localtest.me` to use DNS to resolve to localhost  * http://readme.localtest.me/  */  test('works with localtest.me', async () => {   const server = createServer((req, res) => {-    res.end('ha')+    res.end(JSON.stringify({ url: req.url, headers: req.headers }))   })    await listen(server)   const { port } = server.address() -  const res = await cachedDNSFetch(`http://localtest.me:${port}`)-  expect(await res.text()).toBe('ha')-  server.close()+  try {+    const host = `localtest.me:${port}`+    const res = await cachedDNSFetch(`http://${host}`)+    const body = await res.json()+    expect(res.url).toBe(`http://127.0.0.1:${port}/`)+    expect(body.headers.host).toBe(host)

Added.

TooTallNate

comment created time in 11 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha 7b89212fbaddc8e7bac4e2242ec403dce0489979

Remove `dns`

view details

Nathan Rajlich

commit sha a7c6e6f4897fc58fff1df08a9c8ded5bb960973f

Test `body.url` too

view details

Nathan Rajlich

commit sha ea8fc9708116b146e9036c6f8e6614fa21a32ca3

Merge branch 'fix' of github.com:vercel/fetch-cached-dns into fix

view details

push time in 11 days

PullRequestReviewEvent

Pull request review commentvercel/fetch-cached-dns

Properly set the IP address in the request URL

 /* eslint-env jest*/+const dns = require('dns') const listen = require('async-listen') const { createServer } = require('http') const cachedDNSFetch = require('./index')(require('node-fetch')) +dns.setServers(['8.8.8.8', '1.1.1.1'])

Nope. Wtf.

TooTallNate

comment created time in 11 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha 53255a0b0adf8adb834111592a69538a82a020b4

Fix typo. Thanks @styfle Co-authored-by: Steven <steven@ceriously.com>

view details

push time in 11 days

Pull request review commentvercel/fetch-cached-dns

Properly set the IP address in the request URL

 function setup(fetch) {         opts.headers.set('Host', parsed.host)       }       opts.redirect = 'manual'-      parsed.hostname = await resolve(parsed.hostname)+      parsed.host = parsed.hostname = await resolve(parsed.hostname)+      if (parsed.port) {+        parsed.host += `:${parsed.port}`+      }       url = format(parsed)     }     const res = await fetch(url, opts)     if (isRedirect(res.status)) {       const redirectOpts = Object.assign({}, opts)       redirectOpts.headers = new Headers(opts.headers) -      // per fetch spec, for POST request with 301/302 response, or any request with 303 response, use GET when following redirect+      // Per fetch spec, for POST request with 301/302 response, or any+      // request with 303 response, use GET when following redirect       if (         res.status === 303 ||         ((res.status === 301 || res.status === 302) && opts.method === 'POST')

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

TooTallNate

comment created time in 11 days

PullRequestReviewEvent

PR opened vercel/fetch-cached-dns

Properly set the IP address in the request URL

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.

+80 -45

0 comment

2 changed files

pr created time in 11 days

create barnchvercel/fetch-cached-dns

branch : fix

created branch time in 11 days

release vercel/fetch-retry

5.0.3

released time in 12 days

created tagvercel/fetch-retry

tag5.0.3

Wrapper around `fetch` with sensible retrying defaults

created time in 12 days

push eventvercel/fetch-retry

Nathan Rajlich

commit sha 24bff13d2bfc188644a224f82ffcf1502a8dc650

5.0.3

view details

push time in 12 days

push eventvercel/fetch-retry

Nathan Rajlich

commit sha 379185b73b93569736014774715b5d6128a435a2

Add GH Actions badge to readme

view details

push time in 12 days

push eventvercel/fetch-retry

Nathan Rajlich

commit sha 44571ef9c0ca146f2d5ef05279b2311f3efd26a7

Use GH Actions for CI instead of CircleCI (#39) * Use GH Actions for CI instead of CircleCI * Fix Node 8 * Prettier * Fix test again

view details

push time in 12 days

delete branch vercel/fetch-retry

delete branch : add/gh-actions

delete time in 12 days

push eventvercel/fetch-retry

Nathan Rajlich

commit sha 279ac346502eda1571bde86039ab77f1e25850d2

Fix test again

view details

push time in 12 days

push eventvercel/fetch-retry

Nathan Rajlich

commit sha b4163d034dfe309fdc326197e8a25c3fb366dec6

Prettier

view details

push time in 12 days

push eventvercel/fetch-retry

Nathan Rajlich

commit sha 7c5d4e85e6eca6768101c4f9854c43bb85880351

Fix Node 8

view details

push time in 12 days

PR opened vercel/fetch-retry

Use GH Actions for CI instead of CircleCI
+46 -37

0 comment

2 changed files

pr created time in 12 days

create barnchvercel/fetch-retry

branch : add/gh-actions

created branch time in 12 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha 07f2ef5ffc7d2554e19e3c628e40b38ecf44c8a3

Test Windows

view details

push time in 12 days

push eventvercel/fetch-cached-dns

dependabot[bot]

commit sha 12338c37d3af56d7270831b86073f2b770a9c36c

Bump node-fetch from 1.7.3 to 2.6.1 (#24) Bumps [node-fetch](https://github.com/bitinn/node-fetch) from 1.7.3 to 2.6.1. - [Release notes](https://github.com/bitinn/node-fetch/releases) - [Changelog](https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md) - [Commits](https://github.com/bitinn/node-fetch/compare/1.7.3...v2.6.1) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 12 days

delete branch vercel/fetch-cached-dns

delete branch : dependabot/npm_and_yarn/node-fetch-2.6.1

delete time in 12 days

PR merged vercel/fetch-cached-dns

Bump node-fetch from 1.7.3 to 2.6.1 dependencies

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 compatibility score

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>

+7 -24

0 comment

2 changed files

dependabot[bot]

pr closed time in 12 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha d914f75106ca95f7ed2eb24ada98a16b39bda28e

Add GH Actions badge to Readme

view details

push time in 12 days

delete branch vercel/fetch-cached-dns

delete branch : dependabot/npm_and_yarn/mixin-deep-1.3.2

delete time in 12 days

push eventvercel/fetch-cached-dns

dependabot[bot]

commit sha 158b677ae2ff0d7411b28a39667b3246515b2b59

Bump mixin-deep from 1.3.1 to 1.3.2 (#20) Bumps [mixin-deep](https://github.com/jonschlinkert/mixin-deep) from 1.3.1 to 1.3.2. - [Release notes](https://github.com/jonschlinkert/mixin-deep/releases) - [Commits](https://github.com/jonschlinkert/mixin-deep/compare/1.3.1...1.3.2) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 12 days

PR merged vercel/fetch-cached-dns

Bump mixin-deep from 1.3.1 to 1.3.2 dependencies

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 compatibility score

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>

+3 -3

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha 2b4a4444bf817f168c525ac811135c2516723ffb

Rename to `@vercel/fetch-cached-dns` (#25)

view details

push time in 12 days

delete branch vercel/fetch-cached-dns

delete branch : rename/vercel

delete time in 12 days

push eventvercel/fetch-cached-dns

Nathan Rajlich

commit sha 64f91aabb04e7d8db339b5fa047e48432057abcf

Add GitHub Actions for CI (#26)

view details

push time in 12 days

delete branch vercel/fetch-cached-dns

delete branch : add/gh-actions

delete time in 12 days

pull request commentvercel/fetch-retry

Don’t retry if the request was aborted

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

a-ursino

comment created time in 12 days

push eventvercel/fetch-retry

dependabot[bot]

commit sha f4718fd48c97cd5d088f71fc343df9b0931157b2

Bump node-fetch from 1.7.3 to 2.6.1 (#36) Bumps [node-fetch](https://github.com/bitinn/node-fetch) from 1.7.3 to 2.6.1. - [Release notes](https://github.com/bitinn/node-fetch/releases) - [Changelog](https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md) - [Commits](https://github.com/bitinn/node-fetch/compare/1.7.3...v2.6.1) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 12 days

delete branch vercel/fetch-retry

delete branch : dependabot/npm_and_yarn/node-fetch-2.6.1

delete time in 12 days

PR merged vercel/fetch-retry

Bump node-fetch from 1.7.3 to 2.6.1 dependencies

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 compatibility score

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>

+7 -24

0 comment

2 changed files

dependabot[bot]

pr closed time in 12 days

push eventvercel/fetch-retry

dependabot[bot]

commit sha 4709b0437602bfc8f2b9276a449a79f3057b7e9d

Bump diff from 3.4.0 to 3.5.0 (#20) Bumps [diff](https://github.com/kpdecker/jsdiff) from 3.4.0 to 3.5.0. - [Release notes](https://github.com/kpdecker/jsdiff/releases) - [Changelog](https://github.com/kpdecker/jsdiff/blob/master/release-notes.md) - [Commits](https://github.com/kpdecker/jsdiff/compare/v3.4.0...v3.5.0) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 12 days

more