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

json-proxy-transform

v1.0.3

Published

Simple proxy server with ability to transform JSON request and response.

Readme

json-proxy-transform

This library implements a simple proxy server for JSON HTTP APIs that can transform the request before it goes to the target service and/or the response after it returns from the target service. It is written in TypeScript and is based on Express and Axios.

This proxy is suitable for test environments and test use cases, but is not recommended for production use.

The src/proxy-run-example.ts file contains an example that proxies the Postman echo service (see below) with request and response transformations. The examples in the examples-data directory (see below) can be used to call the proxy service. The Postman collection example files require the Postman app and the curl examples can be used without Postman.

The example-data directory contains:

  • Hello-World.postman_collection.json -- the out-of-the-box Postman collection that uses the Postman echo service to illustrate simple API testing.
  • Hello-Proxy-Post.postman_collection.json -- a modification of the above collection to illustrate the testing of the example transformation functions in src/proxy-run-example.ts.
  • Hello-Proxy-Put.postman_collection.json -- same as the above, but to illustrate PUT requests instead of POSTs.
  • hello-proxy-post-curl.sh -- curl script with same POST request as Hello-Proxy-Post.postman_collection.json.
  • hello-proxy-put-curl.sh -- same as the above, but to illustrate PUT requests instead of POSTs.

To run the example, cd to the directory where this repo was downloaded and run npx ts-node src/proxy-run-example.ts or npm run example.

API documentation

See docs/modules.md.

Implementation note

While Axios directly provides the ability to transform requests and responses, I chose, after much exploration, not to use that feature as it adds much unnecessary complexity to the implementation of this library. The main problem is that much of the default Axios behaviour goes away when transformRequest and transformResponse are used, so it is necessary make calls to JSON.stringify, parse JSON data, set several headers, etc. In addition, the Axios transformRequest function uses the AxiosRequestHeaders type which is different from the standard IncomingHttpHeaders type. To avoid introducing an API dependency on AxiosRequestHeaders, it would be necessary for the implementation to iterate over the latter to make it compatible with IncomingHttpHeaders.