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

connect-json-proxy

v1.0.3

Published

grunt-connect middleware to proxy API requests to remote servers without CORS or JSONP. Based on the json-proxy project, for express.

Downloads

11

Readme

Intro

This is a simple package that wraps the json-proxy package, providing support for multiple endpoints based on an HTTP Header or URL parameter.

It fulfils a specific need for internal applications for us, so is NOT designed to be super high performance or on production sites. (for example, it re-initializes the proxy for EVERY request).

Usage

Assuming that grunt-connect us running on port 9000, and you can call the following URL to get the connect server to redirect the request to somewhere else.

http://localhost:9000/PortalApp/api/v1/some/service/call?apiProxy=LocalhostNode

redirects to the endpoint defined by LocalhostNode (ie, port 8080)...

http://localhost:8080/PortalApp/api/v1/some/service/call?apiProxy=LocalhostNode

Setup

In your Gruntfile.js

var apiProxy = require('grunt-json-proxy').initialize({
    // A 'node' is referenced by name in the 'proxy.forward' section below, instead of a URL.
    nodes: {
        ihportal: {
            // Each endpoint is listed here as in key: endpoint format.
            'Localhost': 'http://localhost:8080/'
        }
    },

    // If no endpoint name is passed in a http header or url parameter, use this one.
    defaultEndpointName: 'Localhost',

    // Proxy's, as defined by json-proxy, however the value of each 'forward' entry is a 'node' (as defined above) instead of a url.
    proxy: {
        forward: {
            '/PortalApp/': 'ihportal'
        }
    }
});


// Define the configuration for all the tasks
grunt.initConfig({

    // The actual grunt server settings
    connect: {
        options: {
            port: 9000,
            // Change this to '0.0.0.0' to access the server from outside.
            hostname: 'localhost',
            livereload: 35729
        },
        livereload: {
            options: {
                middleware: function (connect) {
                    return [
                        connect.static(appConfig.app),


                        // The apiProxy middleware is place HERE
                        apiProxy


                        ]
                    }
                }
            }
        }
    });