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

lint-my-pr

v0.2.0

Published

Add comments to your PR where there are linting issues.

Downloads

10

Readme

Lint My PR

This automates the process of linting pull requests and adds comments to the lines with problems. There are other linters available for Travis, but none of them create comments to mark problem lines, and others require way too much configuration.

Setup is simple.

npm install --save-dev lint-my-pr

Create a new personal Github token, then set up your Travis environment with that token set to GITHUB_TOKEN. See Travis docs for help on that (you can add it either via the command line or via their website).

Then add the script to your .travis.yml file. I'd suggest using the "stages" feature:

- jobs
  include:
    - stage: linting
      if: type = pull_request
      script: lint-my-pr --slug="${TRAVIS_PULL_REQUEST_SLUG}" --pr="${TRAVIS_PULL_REQUEST}"

Using if: type = pull_request ensures that the linter only runs on PR commits.

There are other configuration options available. Here is the complete list.

| Argument | Description | | -------- | ----------- | | --slug | The slug (:owner/:repo) for the pull request | --pr | The issue number of the PR | --dry | Go through the process of linting, but don't create comments on the PR | --token | Manually set a token instead of using the environment variable | --config | Specify the path to your .eslintrc config you want to use | --path | The path you want to lint. This defaults to the root path of the repo