npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

undici-proxy-env

v1.0.0

Published

Make Node's built-in fetch honor HTTP(S)_PROXY — and survive the Clash/corporate-proxy response mangling that silently breaks LLM SDKs.

Readme

undici-proxy-env

Your OpenAI / Anthropic / any-SDK call silently fails behind a proxy — but curl works fine? It's because Node's built-in fetch (undici) ignores HTTPS_PROXY / HTTP_PROXY. One call fixes it — plus the two response-mangling gotchas that local proxies like Clash introduce.

npm i undici-proxy-env
import { configureProxyFromEnv } from "undici-proxy-env";

// Call once, before any fetch/SDK use. Reads HTTPS_PROXY/HTTP_PROXY.
configureProxyFromEnv();            // → true if a proxy is now in effect

// ...now the Anthropic/OpenAI SDK, LangChain, plain fetch, etc. go through it.

The three problems it solves

1. fetch ignores the proxy env vars. Node's http-module clients and curl honor HTTPS_PROXY; fetch/undici do not. So the SDK (which uses fetch) times out or 403s behind a corporate/region proxy while everything else works. configureProxyFromEnv() installs a global undici ProxyAgent from the env — every subsequent fetch goes through it.

2. Clash strips Content-Encoding but sends gzip. Some local proxies (Clash, others) drop the Content-Encoding: gzip header through CONNECT tunnels while still sending gzipped bytes — undici then hands your SDK raw gzip that fails to JSON-parse. We force Accept-Encoding: identity outbound so the upstream returns plain text.

3. Clash drops the response Content-Type. Without it, an SDK treats a JSON body as a string and messages.create() returns text instead of a parsed object. proxyAwareFetch re-injects application/json when the body looks like JSON:

import { configureProxyFromEnv, proxyAwareFetch } from "undici-proxy-env";
import Anthropic from "@anthropic-ai/sdk";

configureProxyFromEnv();
const client = new Anthropic({ fetch: proxyAwareFetch }); // survives header-stripping proxies

(If your proxy doesn't strip headers you don't need proxyAwareFetch — the global agent from step 1 is enough. It's a safe pass-through either way.)

API

| Export | What it does | |---|---| | configureProxyFromEnv(opts?) | Install the global proxy from env. opts.url forces a URL; opts.log(msg) gets a one-line notice. Idempotent. Returns boolean (is a proxy now active). | | isProxyInstalled() | true iff a proxy was installed. | | proxyAwareFetch | A fetch drop-in that repairs a missing response Content-Type. Pass as an SDK's fetch option. |

Node ≥ 18. Zero config beyond the standard HTTPS_PROXY / HTTP_PROXY env vars.

License

MIT © oratis