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

shipit.gifs

v1.0.23

Published

GIFs data for https://shipit.today

Downloads

35

Readme

Build Status

shipit.gifs

The database of GIFs for https://www.shipit.today

How to Contribute

General Rules

  • Be a good person
  • Add GIFs that can be used in the context of shipping code reviews, design reviews or just any "Looks good to me" or "Ship it!" moments
  • You can add as many as you'd like
  • Use GIFs at a reasonable size, no more than 5MB.
  • GIFs should come from one of the approved domains in domains.json
  • GIFs need to pass all tests and be approved in a Pull Request.
  • Keep names all lowercase, the only special character that is allowed is a dash -.
  • Include all fields: _id, name, url, description, active.
  • Don't remove or rename any previously submitted GIFs as they could be used in the wild already.
  • If a GIF is broken, mark the active state to 0 or fix the URL.
  • Add a description so it is easy to understand the content of the GIF without opening it.
  • No graphic content.

Rules that will be tested

  • The existing entries cannot be removed
  • The existing names cannot be changed
  • The _id is required
  • The _id needs to be the same as its index in the array
  • The _id needs to be a number
  • The name is required
  • The name must be less than 50 characters
  • The name must be greater than 1 character
  • The name must be unique
  • The name must only contain lowercase letters, numbers and dashes (-)
  • The name must start with a lowercase letter
  • The url paths must be unique
  • The url is required
  • The url must be less than 2000 characters
  • The url protocol must start with https://
  • The url domain must be an approved domain
  • The url must not have query params
  • The url must not have a fragment
  • The url path must end with .gif
  • The description cannot contain special characters
  • The description is required
  • The description must be less than 200 characters
  • The active state is required

Submitting a contribution

Adding a GIF via cli script

Follow the terminal prompts @ yarn && yarn add:gif

Adding a GIF by hand

Add your gif to the end of the gifs array in gifs.json with the correct JSON structure:

{
  "gifs": [
    {
      "_id": 10,
      "name": "someuniquename",
      "url": "https://foo.com/some.gif",
      "description": "Some description",
      "active": 1
    }
  ]
}

Opening a PR

Run yarn gh:pr to automatically open a PR with your added GIFs rendered in the PR body, otherwise follow the instructions below.

Validating and submitting your entry

  1. Run yarn test to make sure everything passes
  2. Create a pull request with the changed gifs.json file
  3. Make sure to include the GIF in an image tag in the comment section of the Pull Request for easy review
  4. Wait for submission to be approved

Created by @seantomburke ©2020