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

eslint-config-shyp

v1.0.0

Published

An eslint configuration for Shyp projects

Downloads

9

Readme

eslint-config-shyp

An eslint shareable config for Shyp's web projects.

Contributing

  • All changes and proposals should be made in a pull request against this repo. Tag the @shyp/web team for discussion and do not merge changes without making sure everyone's in the loop - any updates here impact many projects.
  • In general, we're very unlikely to add or modify rules in a way that contradicts earlier rules. Changes are generally to enforce something we've decided to avoid, or loosen a restriction that we've found an edge case for. The style prescribed here may not match your personal preferences, but we're aiming for consistency and codifying patterns that we already use, so unfortunately not everyone's tastes will match this at all times.

Usage

Three configurations are currently provided:

eslint-config-shyp

A baseline for linting ES2015+ projects.

Install via:

$ npm install --save-dev eslint eslint-config-shyp

Then in your .eslintrc:

{
  "extends": "eslint-config-shyp",
  ... overwrite any rules as necessary ...
}

eslint-config-shyp/babel

A configuration for projects using Babel.

Installation:

$ npm install --save-dev eslint eslint-config-shyp babel-eslint

eslintrc:

"extends": "eslint-config-shyp/babel"

eslint-config-shyp/react

A configuration for projects using React. Also uses Babel as the parser.

Installation:

$ npm install --save-dev eslint eslint-config-shyp babel-eslint eslint-plugin-react

eslintrc:

"extends": "eslint-config-shyp/react"