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

the-more-the-merrier

v0.0.1

Published

A naive sessions counter to avoid conflicting requests to shared resources

Downloads

4

Readme

the-more-the-merrier

A naive sessions counter to avoid conflicting requests to shared resources.

Imagine you need to simultaneously test several instances of frontend that are assigned to the same huge backend (and it is hard to create another instance of that backend). You want to prevent two or more instances from altering same data objects on the backend.

So a tested frontend instance should know its unique number, but that number cannot be determined internally since multiple instances can be run by different people in different environments simultaneously.

So you just can set up a single the-more-the-merrier server, and obtain session numbers from it.

Usage

make install
make run LISTEN=8080

It sets up a server with following API:

  • POST /foo returns a new session number for key foo
  • GET /foo shows active session numbers for key foo
  • DELETE /foo/n frees session number n for key foo
  • DELETE /foo frees all session numbers for key foo

Example

> POST /test
< 0

> POST /test
< 1

> POST /test
< 2

> GET /test
< [0,1,2]

> DELETE /test/1
< [0,2]

> POST /test
< 1

> GET /test
< [0,1,2]

> DELETE /test/3
< [0,1,2]

> DELETE /test
< []