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

aws-liveness

v1.1.1

Published

AWS Liveness tools

Downloads

94

Readme

Join Slack Build Status Greenkeeper badge

aws-liveness

AWS Liveness tools.

Install

npm i --save aws-liveness

Usage

const AWSLiveness = require('aws-liveness');
const { DynamoDB } = require('aws-sdk');

const awsLiveness = new AWSLiveness();
const dynamoDBClient = new DynamoDB();

// ping and wait services up to 10 seconds
awsLiveness.waitForServices({
  clients: [dynamoDBClient],
  waitSeconds: 10
})
  .then(() => console.log('services liveness ok'))
  .catch(console.error);

// ping a service
awsLiveness.ping({ client: dynamoDBClient })
  .then(() => console.log('dynamodb ping success'))
  .catch(console.error);

Customization

You can customize and/or extend aws-liveness tools to fit your application needs.

const AWSLiveness = require('aws-liveness');
const { DynamoDB } = require('aws-sdk');

class MyCustomService {
  async fetchSomeData () {
    return { foo: 'bar' }
  }
}

const customServices = [{
  test: client => client instanceof DynamoDB,
  ping: client => client.describeTable({ TableName: 'Foo' }).promise()
}, {
  test: client => client instanceof MyCustomService,
  ping: client => client.fetchSomeData()
}]

const awsLiveness = new AWSLiveness({ services: customServices });
const dynamoDBClient = new DynamoDB();
const myCustomService = new MyCustomService();

awsLiveness.ping({ client: dynamoDBClient })
  .then(() => console.log('dynamodb ping success'))
  .catch(console.error);

awsLiveness.ping({ client: myCustomService })
  .then(() => console.log('my custom service ping success'))
  .catch(console.error);

Debug

AWS Liveness uses debug module internally to log information about ping requests and services status. Logging is turned off by default and can be conditionally turned on by setting the DEBUG environment variable equals to aws-liveness.

Examples

Localstack

You can use this module to ensure that LocalStack services are up and running before you test and/or start your application.

// ping-localstack.js
const dynamoDBClient = new DynamoDB({
  endpoint: process.env.DYNAMODB_ENDPOINT
});

if (require.main === module) {
  awsLiveness.waitForServices({
    clients: [dynamoDBClient],
    waitSeconds: process.env.WAIT_SECONDS || 10
  })
    .catch(console.error);
}
{
  "scripts": {
    "localstack": "docker run -it -p 4569:4569 -p 9999:8080 --rm localstack/localstack",
    "localstack-wait": "AWS_ACCESS_KEY_ID=fakeid AWS_SECRET_ACCESS_KEY=fakekey node ping-localstack.js",
    "start": "node app.js",
    "test-e2e": "AWS_ACCESS_KEY_ID=fakeid AWS_SECRET_ACCESS_KEY=fakekey mocha test-e2e/**/*.test.js",
  }
}
DYNAMODB_ENDPOINT=http://localhost:4569 npm run localstack-wait && npm run test-e2e

Contributing

  1. Commits to master must be done through a Pull Request and Squash and Merge option.

  2. Add a title and body that follows the Conventional Commits Specification.