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

travis-github-lint-status-update

v1.0.4

Published

A github integration which displays linter results generated by Travis as a commit/PR status

Downloads

8

Readme

This is a GitHub integration powered by Travis-CI

Why

I wanted to separate Linter results from Test results. I don't believe that continuous integration should fail because of simple linting errors. This module is meant to post Linter results as a separate Status line on a GitHub commit or Pull Request.

Example

Limitations

This module assumes you are working with Travis for CI, GitHub for SCM, and ESLint for linting. Pull requests welcome to extend support.

When linting, the module acts the same as if you called eslint . in your project root.

Setup

First you will need to create a Personal Access Token with the repo:status permission. Add your generated token to your repository's Environment Varibles in Travis-CI as TRAVIS_GITHUB_LINT_STATUS_TOKEN. You can access the Environment Variables in Travis-CI by going to your repository's Settings page on the Travis-CI website.

Next you will need to load this module during your Travis-CI execution. In your install section add npm install travis-github-lint-status. If you don't have an install section, you will need to add one (example in YAML):

install:
  - npm install;
    npm install travis-github-lint-status;

Then the actual call in the script section (again in YAML, replace npm run coverage with whatever your standard CI run script is):

script:
  - ./node_modules/travis-github-lint-status/index.js
    npm run coverage;

Notes

This module should only be run once per commit or pull-request. If your CI is configured to test on multiple platforms or Node versions, you should make sure this module only runs in one particular configuration.

An example:

language: node_js
node_js:
  - "node"
  - "4"
  - "0.12"
os:
  - linux
  - osx
install:
  - npm install;
    npm install travis-github-lint-status;
script:
  - if [ "$TRAVIS_OS_NAME" == "linux" ] && [ "$TRAVIS_NODE_VERSION" == "node" ]; then
    ./node_modules/travis-github-lint-status/index.js;
    fi;
    npm run coverage;

In The Wild

Feel free to explore the pull request statuses, commit statuses, and Travis-CI configs of the following projects: