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

@includable/service

v1.1.0

Published

Base framework for all microservices.

Downloads

4

Readme

Includable microservice base

This repo contains all the basics required to build a microservice for the Includable platform.

Usage

Install using NPM:

npm i @includable/service

Usage information can be found in the example.

Guidelines

Adapters

Only ever enable the adapters that you need, since almost every adapter slows down the startup time of the app, as well as adding dependencies for the app to stay online (database connections etc.)

Currently, the following adapters are available:

  • mysql (using Sequelize)
  • redis
  • queue (using Kue)

REST

All endpoints should use REST HTTP method keywords GET, POST, PUT and DELETE.

Endpoints should always start with their model name in plural:

GET /certificates 			Get all certificates
POST /certificates			Add a certificate
GET /certificates/:id		Get single certificate
DELETE /certificates/:id	Delete certificate

Any IDs or unique identifiers should be formed as UUIDs. When UUIDs have to be generated, always use UUIDv4.

Service independence

Services should be as decoupled from the rest of the platform as possible. That also means avoiding using Includable-specific terms like 'community' or 'reseller' and avoiding directly linking data entries in the database of the server to those types of global entities. Instead, it is a good practice to give every model a field userData, where the consumer of the service can freely add any additional data that they require to later identify to which reseller, community or user a certain entry belongs.

You can set up such a field in a Sequelize model using the following configuration:

userData: {
  type: Sequelize.TEXT,
  allowNull: true
}

User identification

The only exception to that is the notion of a user. What that means exactly and how they are identified may differ from service to service, but a default is to use a UUID string as the user identifier.

This value is known in the main database as an attribute of the user model:

$user = User::find(40);

echo $user->attr('uuid');

In the future, there will also be a getter function on the User model to get this value more easily, simply using $user->uuid.