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 🙏

© 2024 – Pkg Stats / Ryan Hefner

cdn-server

v0.3.0

Published

This is a basic cdn server engine

Downloads

8

Readme

cdn-server

This is a basic cdn server engine

How does it work

First install it:

npm install --save cdn-server

It uses the redis-url-cache node library to store URLs in a redis data store, and bunyan for JSON logging.

It runs on a node.js http server

The config file is straight forward.

Config JSON

The JSON format is:

interface ICDNconfig{
    defaultDomain: string, // When provided with a relative URL, this hostname will be used
    port: number, // listening port
    instanceName: string, // rediurl-cache instance NAme
    redisConfig: RedisUrlCache.RedisStorageConfig, 
    cacheRules: RedisUrlCache.CacheRules
}

instanceName See Instances

RedisUrlCache.RedisStorageConfig See Redis Config

RedisUrlCache.CacheRules See Cache Rules

Note Regexes inside cacheRules must be valid.

Usage

var CacheServer = require('cdn-server');
var bunyan = require('bunyan');

var config = {
    defaultDomain: 'http://127.0.0.1:3000/',
    port: 3030,
    instanceName: 'CACHE',
    redisConfig: {
        host: '127.0.0.1',
        port: 6379,
    },
    cacheRules: {
        default: 'always',
        always: [],
        never: [],
        maxAge: []
    }
}

var logger = bunyan.createLogger({name: 'I am a console logger'});

var server = new CacheServer(config, logger);

server.start( function(err) {
    if(err) throw err;
    console.log('cache server started');
});

Then you can CURL:

curl --header "referer: http://whatever.com" http://127.0.0.1:3030/get?url=http://www.google.com

The referer header is mandatory

Whats wrong with it?

It doesn't supports CORS (yet), although the fix is trivial

This is just a server, if you query http://127.0.0.1:3030/get?url=http://www.google.com&referer=http://whatever.com, inside your browser, you will of course get the correct HTML, but the browser will call the wrong relative URLs.