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

getting-started-microservice

v0.0.3

Published

[![coverage report](https://spokedev.githost.io/fab/getting-started-microservice/badges/develop/coverage.svg)](https://spokedev.githost.io/fab/getting-started-microservice/commits/develop)

Downloads

1

Readme

Getting Started Microservice

coverage report

pipeline status

This repository provides a template for FAB microservice delivery.

Usage

Fork Template Change Project Name in package.json, API & product definitions files and deploy/deployment.yaml Push to repository and check pipeline passes.

Rules

Changes are to be made in the given folders and follow the router-controller-adapter pattern.

All code needs test coverage!

Code must

Logs

Log messages should follow the given patterns including naming of messages as msg and errors as err:

Debug messages provide additional context in development

logger.debug({ msg: 'Error From DAS Adapter. Returning' });

Info messages provide production logs of non-error events

logger.info({ msg: 'Successfully Created Client' });

Error messages provide context as close to the source of an error as possible.

logger.error({ err, msg: 'Unhandled Error From DAS Adapter' });

Fatal messages provide details of fatal events. Fatal events should stop the server to fail fast.

logger.fatal({ err, msg: `ERROR LOADING SCHEMAS: ${e.message}` });
process.exit(1);

Metrics

Metrics are exposed through the metrics module of fab_utils. Increment with: metrics.increment('clients');