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

@steinerjing/gutterball

v1.0.4

Published

Utilities without bumpers

Downloads

5

Readme

GutterBall

An amazong collection of one utility.

Utilities:

  • FileActor
  • <end of list>

FileActor

Provides a handy function to persists data by reading from and writing to a JSON file in only a one or few lines of code.

Import

ESM

import { fileActor } from '@steinerjing/gutterball'

CJS

const { fileActor } = require('@steinerjing/gutterball')

Reading Data

The following is a shorthand way to read all data from the JSON file.

const allData = fileActor('./data/counters.json', data => data)

To get more specific data, create a seperate object and return it in the callback. This example returns an array of all users with admin rights:

const allData = fileActor('./data/counters.json', data => {
    return data.users.filter( user => user.isAdmin )
})

Changing Data

To change persistant data, make changes to the data parameter in the callback. Note that you can not change the data object itself because it is the arguemnt, but you can change any attribute about the data. The changes will persist automatically.

The following example gives all users admin rights:

fileActor('./data/counters.json', data => {
    data.users.forEach( user => user.isAdmin === true )
})

Reading and Changing Data

Reading and changing data can both take place in the callback. As an example, the following gives all users admin rights and returns the number of total users.

fileActor('./data/counters.json', data => {
    data.users.forEach( user => user.isAdmin === true )
    return data.users.length
})

The following example increases a counter and returns the pervious counter value each time it is called. The changes are stored in the JSON file provided by the first argument. If the file doesn't exist is will be created. The data stored in the JSON file must contain an object as the root, not an array.

const newID = fileActor('./data/counters.json', data => data.nextMessageID++)