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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@eahefnawy/s

v1.0.4

Published

Build serverless libraries on AWS

Downloads

27

Readme

Install S:

npm i -g @eahefnawy/s

Start building your serverless library by creating an index.js file that exports your functions, and an optional config object:

const createUser = async (args) => {
  // create user here...
  return user
}

const updateUser = async (args) => {
  // update user here...
  return user
}

const deleteUser = async (args) => {
  // delete user here...
  return user
}

const config = {
  name: 'users', // defaults to parent dir name
  region: 'us-east-2', // defaults to us-east-1
  description: 'library of user functions', // defaults to "S: Build serverless libraries on AWS"
  memory: 512, // defaults to 128
  timeout: 300, // defaults to 10
  env: {
    SOME_TOKEN: 'abc'
  },
  origins: ['example.com'] // origin domains authorized to access your library. defaults to *
}

module.exports = { createUser, updateUser, deleteUser, config }

Sync your serverless library. Notice the returned SID:

$ s
✔ SID: a-qwertyuiop (copied to clipboard)
$

Now you can use your new serverless library by passing the SID and importing the functions you'd like to use:

const S = require('@eahefnawy/s')

const config = {
  SID: 'a-qwertyuiop',
  import: ['createUser', 'updateUser', 'deleteUser']
}

const { createUser, updateUser, deleteUser } = S(config)

const createdUser = await createUser(args)

const updatedUser = await updateUser(args)

const deletedUser = await deleteUser(args)

Check the logs of your serverless library:

$ s logs
Today at 12:02:14 PM Function Called: createUser
Today at 12:02:14 PM Created User eahefnawy
Today at 12:25:59 PM Function Called: updateUser
Today at 12:25:59 PM Updated User eahefnawy
Today at 12:34:12 PM Function Called: deleteUser
Today at 12:34:12 PM Deleted User eahefnawy

Pro Tip: Changing the name or the region results in a new SID. You can make use of environment variables to create different stages based on the library name:

const config = {
  name: `users-${process.env.S_STAGE}`
}

module.exports = { config }