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

@app-press/eslint-config

v2.0.2

Published

App Press' ESLint rules

Downloads

85

Readme

eslint-config

This package provides App Press' .eslintrc.json as an extensible shared config.

Usage

A few ESLint configurations are exported for convenience; all exports allow for standard testing frameworks (Mocha, Jasmine, and Jest):

eslint-config

The default export contains all ESLint rules, including ES6 and React, and tries to find a balance between traditional server-side and client-side code styles. For this reason, it does not use modules for client-side code by default; thus, the following code will not pass linting:

import React from "react";

But this will:

const React = require("react");
  1. npm install --save-dev @app-press/eslint-config eslint eslint-plugin-react
  2. Add "extends": "@app-press/eslint-config to your .eslintrc file

eslint-config/node

This export is for use on server-side-only code and will not lint React (though it will lint ES6).

  1. npm install --save-dev @app-press/eslint-config eslint
  2. Add "extends": "@app-press/eslint-config/node to your .eslintrc.json file

eslint-config/client

This export is for use on client-side-only code and will lint React (including JSX) and ES6 code.

  1. npm install --save-dev @app-press/eslint-config eslint
  2. Add "extends": "@app-press/eslint-config/client to your .eslintrc file

eslint-config/client-modules

This export is for use on client-side-only code and will lint React (including JSX) and ES6 code. It will also expect that all client-side code is ES6 module based (and thus will assume strict by default).

  1. npm install --save-dev @app-press/eslint-config eslint
  2. Add "extends": "@app-press/eslint-config/client-modules to your .eslintrc file

To override specific rules, simply add a rules section to your .elintrc.json and add your desired rules — they will take precedence.

You may also modify the parser, parserOptions, etc. Just include those sections as well.