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

synchronize-cli

v1.5.1

Published

![CI Status](https://github.com/hershal/synchronize-cli/actions/workflows/node.js.yml/badge.svg)

Downloads

3

Readme

Synchronize CLI

CI Status

Concurrency tools in your CLI.

Synchronize lets you chain long-running tasks together so you can do less babysitting and take longer coffee breaks.

How to use

Synchronize comes with two tools: syn and ack. syn sends the "synchronize" signal, and ack waits for the "synchronize" signal before exiting. You can use these two tools to run and synchronize tasks that depend on this signal by using &&. For example,

On window 1 you have this running:

$ ./do-something.sh && syn something-cool

And on window 2 you have this running:

$ ack something-cool && ./toggle-light.sh

The ./do-something.sh might take a while to finish, so we use syn to signal when it's done. Then we use ack to wait until it gets the signal, and then run whatever needs to be run afterward. Since ack doesn't exit until it gets the signal, the ./toggle-light.sh won't execute until ack receives a syn. Makes sense?

Basic Synchronization Named Barriers

Limitations

Synchronize only works on the current host, not between two different computers. Sucks, I know. Maybe in the future it'll support networked sockets for synchronization. File a bug if you really want it.