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

@epublishing/eslint-config-epublishing

v0.4.2

Published

ePublishing JavaScript Coding Standards for ESLint

Downloads

477

Readme

ePublishing ESLint Configuration

Copyright (C) 2017, ePublishing, Inc.

Installation Steps

1. Peer Dependencies

First, install this package's peer dependencies and save them to your project's package.json file in devDependencies:

$ cd my_epublishing_project
$ npm install --save-dev eslint eslint-plugin-import eslint-plugin-react

Optional Alternative

You can simplify this step by using an external utility instead of the command in the above example:

# This first command only needs to be run a single time. It will install
# a CLI utility called "install-peerdeps" as a global Node module:
$ npm install --global install-peerdeps

# Once you've installed the utility, run it from the root of your project:
$ install-peerdeps --dev @epublishing/eslint-config-epublishing

2. Install this Package

$ npm install --save-dev @epublishing/eslint-config-epublishing

3. Configure ESLint

Create a file named .eslintrc in the root of your project and give it the following contents for starters:

{
  "extends": [ "@epublishing/epublishing" ]
}

You can then add additional configuration to your .eslintrc to override any of the defaults defined by this package. See the ESLint docs for more information.

Usage

Command Line

ESLint will automatically use the project's .eslintrc file, so all you have to do in order to lint your scripts in terminal is:

# Install the eslint CLI utility if necessary:
$ npm install -g eslint

# Lint all .js files in found in app/js against configured rules:
$ eslint app/js/**/*.js

Editor Integration

Plugins that provide inline error reporting are available for most editors and IDEs:

Release Workflow

This repository includes bumped as a development dependency and defines a few hooks to simplify the process of publishing a new release to Bitbucket and the NPM registry.

npm run release $TYPE

Where $TYPE can be any of the release arguments accepted by the bumped release command.

Examples

Fix a bug and publish a new patch release:

$ npm run release patch

  > @epublishing/[email protected] release /home/mike/development/work/eslint-config-epublishing
  > bumped release "patch"


  bumped Releases version 0.1.2.

  post bumped Starting Publishing tag to Bitbucket
  post bumped Everything up-to-date
  post bumped To bitbucket.org:epub_dev/eslint-config-epublishing.git
   * [new tag]         v0.1.2 -> v0.1.2
  post bumped Finished Publishing tag to GitHub after 1.9s.

  post bumped Starting Publishing to NPM
  post bumped + @epublishing/[email protected]
  post bumped Finished Publishing to NPM after 3.9s.