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

seqpar

v1.1.1

Published

seqpar is a batch executor run in sequential & parallel

Downloads

8

Readme

seqpar

Greenkeeper badge npm GitHub license CircleCI

seqpar is a batch executor run in sequential & parallel.
It's easy to create efficient build process.

seqpar_beautify

Install

npm i -g seqpar

Requirement

  • Node.js 6+

Defint first batch file

All batch files are named in {GROUP}_name(.{ext}) (e.g. 000_init.js, 01_lint.sh, 999_failover).

#!/usr/bin/env bash

echo 'Hello, seqpar!'
console.log('Hello, seqpar!')

Executable order and parallelism

Same GROUP run in parallel, different group run in sequential.

000_init
010_bootstrap_npm   <- Run in parallel
010_bootstrap_pods  <- Run in parallel
010_bootstrap_cargo <- Run in parallel
020_lint
030_build
040_tag                <- Run in parallel
040_generate_changelog <- Run in parallel
040_prepublish         <- Run in parallel
999_publish

Usage

seqpar [DIRECTORY]

Options:
  --help             Show help                                         [boolean]
  --version          Show version number                               [boolean]
  -p, --concurrency  Specify the maximum number of concurrency
                                                           [number] [default: 4]
  -b, --bail         Bail after first test failure     [boolean] [default: true]
  -r, --recursive    Include sub directories          [boolean] [default: false]
  --reporters        Specify the reporter to use             [default: ["file"]]
  --runtimes         Use the given runtime(s) to execute files
                                            [default: ":bash,bash:bash,js:node"]

Examples:
  seqpar 'scripts/**/*.js'                  Using glob pattern
  seqpar --recursive scripts                Using recursive flag
  seqpar --no-bail 'scripts/**/*.js'        Run all process even if one or more
                                            process returns not-zero status
  seqpar --concurrency=2 scripts            Specify concurrency
  seqpar --runtimes=':sh,coffee:coffee,ts:ts-node' scripts

For more information, find our manual at https://github.com/Leko/seqpar

Contribution

seqpar welcomes all contributions from anyone.

  1. Fork it
  2. Run npm install
  3. Commit your changes
  4. Send pull request to master branch