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

prlatch

v0.0.13

Published

automate pr review workflow

Downloads

1

Readme

What is PR Latch?

Latch is a tool to help streamline the process of reviewing pull requests. It displays the latest pull requests given a repo and automates the process of starting up environments so you spend less time at the command-line and more time contributing.

Installation

# install globally
npm i -g prlatch

Initialization

First, ensure there is a created personal access token for usage with the Github API.

# prompts for github credentials and generates default .latchrc.json
latch init

Commands

init                         creates .latchrc.json with default values
env-up [project-aliases...]  starts the server for each project alias stipulated
env-down                     stops all project servers
env-new                      prompt to create a new project and updates .latchrc.json
list                         lists all projects in .latchrc.json
review <project-alias>       shows all open PR's on the projects repo

Creating a new environment

The first time env-new is ran, you will be prompted for the main project directory. This is an absolute path to your code folder (Note: projects will not be available for selection if they are not in this directory)

There will be a prompt for an alias, which is a shorthand to start the project's PR review flow or server.

Start command uses the command to start the project. E.g: npm start.

Port is... well, it's the port.

? What is a good alias for this project? example-alias
...
# Example alias usage
latch env-up example-alias
latch review example-alias
...
? Start command: npm [start | run dev | storybook | etc...]
? What port does this project run on? 3030

Running the Project Envs

env-up takes a space-delimited set of projects and runs each project in the background.

latch env-up alias-one alias-two

To kill these background processes running on the given ports:

latch env-down

Review Flow

latch review <project-alias> offers a selection of the current open pull requests in the repo. Selecting an pr will git fetch, checkout, and pull the latest code changes for the given project and pull request. It will then open the default browser to view the PR and proceeds to open the directory with VSCode.

Where are the tests?!?

Meh. Piss off. ;)