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

colosseum

v0.8.1

Published

A microservice platform.

Downloads

9

Readme

Colosseum

Travis npm

A Node JS microservice platform.

A service is a function which accepts a single colosseum parameter. This means that a service can be written without any explicit dependency on Colosseum, which means that the service does not need updating for new versions of Colosseum.

The colosseum object abstracts the way in which services communicate. Each service can handle specific messages using colosseum.handle(message, handler). A service can send a message using colosseum.message(service, message, payload).

Since a service is just a function which operates on the abstract colosseum object, we can run and manage services in many different ways. The simplest is to run all the services inside the same process. More robustly, you could run each service as a separate process on the same machine. To scale, you can run separate services on separte servers. All this is possible without changing the way in which a service is authored.

Usage

Install

npm install --save colosseum

Use

// index.js

import colosseum from 'colosseum';

const options = {
  port: 8080,
  secret: 'my-secret-used-for-json-web-token-generation',
  hash: 'hash-of-password-generated-using-colosseum-hash',
  installDirectory: '/path/to/install/directory'
};

colosseum(options).then(() => {
  console.log('Colosseum is running.');
}).catch((error) => {
  console.error(error.stack);
});

Run

node index.js

Verify Colosseum is running by visiting http://localhost:8080/status

Endpoints

Status

GET /status

Returns 200 👌 if everything is running well.

Authenticate

POST /authenticate

Body { "password": "your-password" }

Returns { "token": "123456" }

Message

POST /<service>/<message>/<token>

Body can be any custom payload for service to handle.

Returns { "success": BOOLEAN, "response": CUSTOM_SERVICE_RESPONSE }