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

the-plumber

v1.0.2

Published

Node application to make sure two files always have the same content.

Downloads

13

Readme

plumber

Plumber helps to make sure two given files always have the same content.

Installation

Plumber runs on Node.js. Please install Node if you haven't already.

Then, in your terminal:

npm install the-plumber -g

Usage

$ plumber connect [source-file] [destination-file]

Plumber then creates a "pipe" (*nix daemon that runs indefinitely) between the two files, making sure subsequent changes to the source-file are reflected in the destination-file.

Since the pipe runs indefinitely in the background, you need to stop it when you no longer want changes piped down to the destination file.

$ kill -9 [pipe-pid]

The pipe-id is returned on creating the pipe. Please see the example below.

Example

Say we're writing an open-source WordPress plugin for Cyclos, and we want to continuously test this plugin with our local WordPress instance while developing it, but our folder for open source projects differs from where the plugin is actually installed.

We can create a pipe connecting the plugin file from our version-controlled, open-source folder to our local WordPress plugins' directory like so:

$ plumber connect /home/opeadeyomoye/open-source/cyclos/wp-cyclos.php $WWW_ROOT/wordpress/wp-content/plugins/wp-cyclos.php

Plumber returns something like:

=======================================================
====================== Plumber ========================
=======================================================


A new pipe has been created!
Further changes to "/home/opeadeyomoye/open-source/cyclos/wp-cyclos.php" will now be piped to "/var/www/html/wordpress/wp-content/plugins/wp-cyclos.php".


This process is running in the background with the PID: 15420.
To stop it, try:


$ kill -9 15420


Thank you for using Plumber!

Credits

Contributing

Open an issue or create a PR if you:

  • found a bug,
  • made some improvements,
  • need to teach some of these young developers the real history of Javascript.

License

Released under The MIT License. See LICENSE file for more details.

Copyright (c) 2017-present, Ope Adeyomoye.