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

@emerson-eps/eslint-config

v6.1.8

Published

Shared ESLint config for Emerson E&P Software

Downloads

3,828

Readme

Shared ESLint Config

GitHub Workflow Status GitHub license npm (scoped) semantic-release Conventional Commits

This is the home of the shared E&P Software ESLint configs. The default config should be used for all React Typescript projects in E&P Software.

Usage

The ESLint config and Prettier config must both be added to get the full shared configuration.

(1) Install the shared Prettier and ESLint configs

npm install --save-dev @emerson-eps/prettier-config @emerson-eps/eslint-config

If you have not already installed prettier and eslint install those as well:

npm install --save-dev prettier eslint

(2) Configure Prettier

Add @emerson-eps/prettier-config to your .prettierrc.js:

module.exports = {
  ...require("@emerson-eps/prettier-config"),
};

For more advanced setups, including how to override settings, see the instructions in the @emerson-eps/prettier-config repository.

(3) Configure ESLint

Specify the package in the extends section of your ESLint configuration:

{
  "extends": "@emerson-eps/eslint-config",
  "rules": {
    // Additional rules...
  }
}

List of current rules

The list of applied rules can be found here

Running ESLint on your code

Add a lint script to your package.json, for example:

{
  "scripts": {
    "lint": "eslint . --max-warnings=0"
  }
}

Code can then be linted with:

npm run lint

CI pipelines should be configured to fail on linting warnings.

Integration with Visual Studio Code

If not already installed, install the Prettier and ESLint extensions.

Overriding the shared configs

Try not to override the shared configs unless you really need to. If you must override them please consider proposing the override as a change to the relevant repository first to avoid divergence of code styles in different projects.