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

banker-asl

v0.2.9

Published

A full-featured asset serving layer for single-page apps

Downloads

21

Readme

Banker

Build Status Code Climate Test Coverage Dependency Status devDependency Status

Deploy

Banker is an asset serving layer built for single-page apps. It's built around the same conventions as ember-cli-deploy, meaning that it expects to find various index.html files available in a Redis server.

Key | Value ------------------|---------- myapp:current | myapp:7fa8d0 myapp:7fa8d0c | <html>...</html> myapp:48180ab | <html>...</html> myapp:857f81a | <html>...</html>

The general idea is that you have an app that manages the data in Redis (via developer deploys, CI pipeline, etc...) and this little server keeps running, eventually making your new static assets available with zero downtime.

Requirements

  • Node.js >= 5.0.0
  • Somewhere to deploy this app (i.e., Heroku)
  • A Redis server (i.e., Heroku free Redis)

Basic Configuration

The one simple way of configuring banker is by environment variables

General Configuration

Variable | Required | Default | Description ------------------|----------|---------------|------------------------ APP_NAME | yes | | App name to use when looking for versions in Redis PORT | no | 3000 | Port to serve assets on

Redis configuration

Variable | Required | Default | Description -----------------------|----------|---------------|------------------------ REDIS_URL | yes | | Redis url

Advanced Configuration

Banker can be consumed as a library in your own simple node.js app. You can then specify URL patterns to map to "apps" using regular expressions.


const BankerServer = require('banker-asl/server');
const RedisDataSource = require('banker-asl/datasource/redis');

let server = new BankerServer({
  datasource: new RedisDataSource({
    url: 'redis://username:[email protected]:12345',
    apps: {
      myapp: {
        forceHttps: true, // Incoming http requests will be redirected to https
        respondTo: [/^myapp.herokuapps.com/, /^myapp-old.herokuapps.com/]
      },
      myotherapp: {
        respondTo: [/^www.myotherapp.com/]
      },
      noappfound: {
        respondTo: [/^.*/]
      }
    }
  }),
});

server.listen(3000);