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-synacor

v3.0.5

Published

ESLint configuration for Synacor javascript projects

Downloads

4,857

Readme

eslint-config-synacor

npm Build Status Greenkeeper badge FOSSA Status

Standard eslint rules for all Synacor javascript projects

Use these rules in your project

Installation

Add eslint-config-synacor as a development dependency for your project: npm i -D eslint-config-synacor

If you aren't already including eslint with your project, install that as a development dependency as well: npm i -D eslint.

Configuration

package.json

To specify for your entire project to use the global rules, add this as a clause in your package.json file:

"eslintConfig": {
	"extends": "eslint-config-synacor"
},

.eslintrc

Optionally (or in addition to your package.json setup), to specify to use the global rules in all subdirectories of a given directory, you can create a .eslintrc file with the contents

{
    extends: 'eslint-config-synacor'
}

Add/Override Rules For Tests test/.eslintrc

There are a set of overrides/rules for directories that contain unit tests. These are available in the test-rules submodule of the package. You can reference them via estlint-config-synacor/test-rules. So, to apply these as overrides in your tests/ directory, you would create a .eslintrc file in tests/. The contents of that file would look like:

{
    extends: 'eslint-config-synacor/test-rules'
}

Developing

All rule definition files are in src/rules. Edit/create rule files there.

Rules that are meant to be used for an entire project should go in files that are included by src/index.js.

Rules that are only meant to be run/overriden in test directories of a project should be included by src/test-rules.js.

License

FOSSA Status