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

@firstandthird/arc-rapptor

v8.0.0

Published

arc-rapptor for serving pages on AWS Lambda

Readme

arc-rapptor

A helper for serving webpages on Lambda using arc.codes

installation

npm install arc-rapptor

usage

const { config, log, aug, logRequest, reply } = require('arc-rapptor');

These work as follows:

config

config will be an object containing configuration information. It will include the contents of @architect/shared/conf/default.json as well as conf/default.json. You can also specify conditional config info in conf/dev.json, conf/staging.json , conf/prod.json and arc-rapptor will include the appropriate configuration depending on what NODE_ENV you are using. This helps development by making it easy to switch between production and development credentials. In addition you can use in-line json variables like so:

{
  "character": {
    "name": "garfield",
    "type": "cat",
  },
  "fullName": "{{character.name}} the {{character.title}}"
}

log

  log(['warning'], 'something is not right!')

log is a logging function provided by logr-all that comes with a number of plugins that can send logged info to a variety of outputs. It can be configured using config.log in your configuration. If you do not specify anything, by default logr-all will have the following settings in config:

log: {
  initLog: false,
  unhandledRejection: true,
  uncaughtException: true
}

aug

aug is an object merging and cloning function. It works similar to Object.assign except that it merges sub-objects:

const obj1 = {
  subobj: {
    var1: 'this comes from obj1',
    var2: 'this comes from obj1'
  },
  name: 'comes from obj1'
};
const obj2 = {
  subobj: {
    var1: 'this was overwritten by obj2 during merge'
  },
  match: 'comes from obj2'
};
const mergedObject = aug({}, obj1, obj2);
  /*
  mergedObjecdt will be:
  {
    subobj: {
      var1: 'this was overwritten by obj2 during merge',
      var2: 'this comes from obj1'
    },
    name: 'comes from obj1',
    match: 'comes from obj2'    
  }
  */

logRequest

logrequest is just a simple helper for logging info from the incoming HTTP request objects:

  logRequest(request);
  /*
  will call:
    log(['request'], { message: `${request.method} ${request.path}`, path: request.path, query: request.query });
  */

reply

is a useful tool for returning valid HTTP responses with the appropriate headers and body:

return reply.html('<body> hi </body>', 201);
.
.
.
return reply.json({ error: 'This is an HTTP 500 error', reason: 'because' }, 500);
.
.
.
return reply.redirect('https://firstandthird.com', 'permanent');