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

chronologically

v1.1.2

Published

A task runner. Do not use. Yet.

Downloads

4

Readme

Chronologically

What is this?

chronologically is a task/process runner. A config file is interpreted as a series of jobs to perform. If a job needs to poll a server before starting, it will do that.

Motivation

Ran into a situation at work in which our development tooling doesn't behave as intended.

<script-name> run dev

This command should:

  • Start my development server
  • Launch an Electron-based container

But instead it only performs the first job with no word as to what's happening with the second.

chronologically isn't meant to be a package for widespread use, but for personal use in places where I need to ensure tasks that impact my day-to-day development are in my control.

How to use

npm install chronologically

chronologically <path-to-config-file>.json

Config


type Message = 'default'|'warning'|'error'

type Job = {
  id?: string; // shall be autogenerated
  name: string; // name of the job
  command: string; // command of the job
  args?: string[]; // command args
  message?: string; // message emitted before running job
  options?: SpawnOptions; // options reference: https://nodejs.org/api/child_process.html#child_processspawncommand-args-options
  // see options here: https://github.com/jeffbski/wait-on
  waitOn?: WaitOnOptions; // should the job wait for other dependencies before running?
  messageForwarding?: MessageType[]; // what messages shall emit to the user's console?
  saveLog?: boolean; // write log to disk?
};

type Config = {
  logOutDir?: string;
  jobs: Job[];
};