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

@beetcb/sstore

v0.3.0

Published

store things at severless function runtime

Downloads

35

Readme

npm

What the hack is sstore?

serverless-store is how you store tiny things at serverless function runtime temporarily,inspired by conf.

When to use it?

When you have a tiny piese of data(an expiring access-token, for example), sstore stores it for you to path /temp/conf/${md5('conf.json').

Better yet, sstore won't block any code execution during runtime.

How to use it?

const sstore = require('@beetcb/sstore')

exports.main = () => {
  // If `secret` is undefind, set it
  console.log(sstore.get('secret') || sstore.set('secret', 'xxx 🕊'))
  // Code logic is done, starts storing,
  sstore.close()
}

sstore.<method>:

  • get(key): get key's value
  • set(key, value): set key using value
  • del(key): delete key's value
  • clear(): delete all the key value pairs
  • close(): This is where the sstore really starts to store