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

readyator

v2.0.0

Published

Waits for localhost ports to be ready before running a supplied command.

Downloads

387

Readme

Readyator

Language Details License Dependency Updates Package Version

Waits for specified urls or ports on localhost to be ready before running a supplied command.

Installation

npm

npm install readyator

Yarn

yarn add readyator

Usage

Preface

  • Addresses (ports or urls) must be separated by comma if you want to check for multiple services to be ready ( returning a successful HTTP status code).
  • Your command must be surrounded by quotes so that it can be properly parsed.
  • The default check interval is 1s (1000ms) but can be changed.

Wait for ports

Command:

readyator [ports] [command]

Example:

readyator 8080,8081 "npm run start"

If you're not looking to perform any specific actions but simply want to determine when the service is available, use this command:

readyator 8080,8081 "exit 0"

Wait for URLs

Command:

readyator [urls] [command]

Example:

readyator https://www.google.com/,http://localhost:8081/ "npm run start"

Change check interval

Command:

readyator [urls] [command] [interval_in_millis]

Example:

readyator https://www.google.com/ "npm run start" 5000

Wait for healthy Docker container

Command:

readyator-docker [container_name] [interval_in_millis]

Example:

readyator-docker my_docker_container 1000

Node.js API

You can use readyator also through its Node.js API:

import readyator from 'readyator';

await readyator([8080, 8081], 'npm run start');

It also supports executing a callback function:

import readyator from 'readyator';

const callback = () => {
  console.log('System is online!');
};

readyator([8080, 8081], callback);

Readyator's programmatic interface can also be used to listen for Docker containers to become healthy:

import {runWhenHealthy} from 'readyator';

await runWhenHealthy('my_docker_container');

Development

Here is how you can easily test the readyator from your development environment when checking out the code:

npm start https://www.google.com/ "npm run exit"