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

repository-warden

v3.2.0

Published

Print out warden information in your repository

Downloads

9

Readme

Warden

Warden is a tool for managing repository ownership.

Ownership of a specific area is signified by creating a .warden file in the folder, any subfolders are also owned by that warden, unless another .warden file exists.

Warden compares your current working branch against default to generate a list of changes, then identify the person from the relevant warden file for a change path.

Installation

Warden requires Node.js v4+ to run.

Then:

$ npx repository-warden

Usage

Repository-warden takes a few commands,

$ warden -V, --version

Will print the version number.

$ warden -h, --help

Will print a simple 'help' message with a summary of commands.

$ warden dir <file path>

Will print warden file information for the given directory within the project. If no path is given, defaults to current working directory.

$ warden

Without commands, will print warden file information for every change on your branch against default.

Development

Clone this repo from GitHub, navigate to the root directory of repository-warden:

$ cd path/to/repository-warden/

And create a link token with:

$ yarn link

Provide this link token to your project repository with:

$ yarn link repository-warden

This will override your global installation with the locally served code.

Now, back to the repository-warden path:

$ yarn watch

Will start serving the local version of the program.

Calls to warden from your linked project repository will respond from this local version.