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 🙏

© 2026 – Pkg Stats / Ryan Hefner

remotely-cli

v1.0.9

Published

Watch and automatcally sync directories remotely

Readme

Rsyncing simplified, push, pull, watch.

Table of Contents

Prerequisites

  • rsync

Install

npm install -g remotely-cli

Usage

Create remotely config (.remotely.json)

$ remotely init

Run this in any parent directory from where you are going to be running remotely.

Remotely will climb up and use the first config file it finds Read about config here

Make sure you edit your config (.remotely.json) file after doing this.


Watch local directory for changes and rsync push on change

$ remotely watch

Rsync pull down remote

$ remotely pull

Rsync push to remote

$ remotely push

Config

Remotely will look for the config file .remotely.json in any directory above where you call remotely [command]. This means that the config can belong anywhere, as long as remotely can find it by traversing upwards

| Config | Desc | | | ------------- |:-------------:|:-------------:| | local | local path to sync dir | required | | remote | remote host and path | required | | rsync_flags | flags to customize rsync | optional | | dry_run | perform dry run | optional | | exclude | files or directories to exclude | optional | | notify | notify when complete | optional |

Example config

This could live in /Users/charliebodman/documents/example/.remotely.json You can create remotely config by calling remotely init

{
    "local":"/Users/charliebodman/documents/example/project",
    "remote":"[email protected]:~/example/project"
}

Maintainers

@charlesbodman

Contribute

PRs accepted.

License

MIT © 2017 Charles Bodman