PiratProxies

Web scraping

Proxies in Node.js fetch: working examples

The fetch built into Node.js does not read a proxy from its options. It uses the undici library underneath, and undici's ProxyAgent is how you give it one.

The right proxy type for Node.js fetch

For most scraping, Residential Lite is the cheapest way to get home IP addresses in the right country. Use Residential when you need a particular state or city, and Unlimited Datacenter for targets in the United States that do not block data centre addresses.

The values to enter in Node.js fetch

Every PiratProxies plan comes down to four values: host, port, username and password. Here they are for Residential; your own username and password are on your plan page.

Hostresi.piratproxies.com
HTTP port8080
SOCKS5 port1080
UsernameUSERNAME
Passwordshown on your plan page

Written as a single address:

http://USERNAME:PASSWORD@resi.piratproxies.com:8080

There is no separate country or session field: both are part of the username. Your plan page has a generator that writes it, and Targeting and sessions describes each piece.

Setting it up in Node.js fetch

  1. Install undici and import ProxyAgent and fetch from it.
  2. Pass the agent as dispatcher with each request.

Code: Node.js fetch through a proxy

Node.js

import { ProxyAgent, fetch } from 'undici';

const dispatcher = new ProxyAgent('http://USERNAME:PASSWORD@resi.piratproxies.com:8080');
const res = await fetch('https://api.ipify.org', { dispatcher });
console.log(await res.text());

Put your own login from the plan page in place of USERNAME and PASSWORD. The example calls an IP-check service, so what it prints is the address your request came from.

Should Node.js fetch rotate IPs or keep one?

When Node.js fetch is fetching lots of unrelated pages, leave the session out of the username and each request gets a fresh IP address. When requests belong together, such as a login, a basket or paginated results that set cookies, put a session in the username so they all share one address.

Here is what a sticky username looks like:

USERNAME-country-us-time-600-session-a1b2c3d4

When Node.js fetch will not connect

  • Import fetch from undici as well. Mixing the global fetch with a ProxyAgent from a different undici version can fail with an unhelpful error.
  • The older node-fetch package takes an agent instead: use https-proxy-agent with it.
  • Error 407 means the login was refused. Copy the username and password from your plan page once more, and make sure no space crept in and the username was not cut short.
  • An IP in the wrong country nearly always comes from the username, since the country code lives there. Other fixes.

Node.js fetch and proxies: questions

Which PiratProxies plan suits Node.js fetch best?

For most scraping, Residential Lite is the cheapest way to get home IP addresses in the right country. Use Residential when you need a particular state or city, and Unlimited Datacenter for targets in the United States that do not block data centre addresses.

Words used in this guide: web scraping, rotating proxy, sticky session, rate limiting, headless browser.

Node.js fetch belongs to its own developers, and PiratProxies has no connection with them; we name it only to say what this guide covers. Follow the rules of the sites you visit and our acceptable use policy.