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

v1.1.1

Published

A principle-based ESLint configuration for projects supporting TypeScript, React, and Jest

Downloads

86

Readme

eslint-config-principled

A principle-based ESLint configuration for projects supporting TypeScript, React, and Jest

Linting Principles

1. Correctness

The linter should treat all (likely) logical mistakes as errors.

2. Consistency

When the readability of different styling options is not situational, the linter should use warnings to enforce one style for consistency.

3. Flexibility

When the readability of different styling options is situational, the linter should not enforce any style in order to give the developer freedom to choose which style is best for the particular situation.

Using eslint-config-principled

First, install the package and its peer dependencies:

npx install-peerdeps eslint-config-principled --dev

For JavaScript projects, extend principled in your local .eslintrc.json configuration file:

{
  "extends": [
    "principled"
  ]
}

For TypeScript projects, extend principled/typescript instead:

{
  "extends": [
    "principled/typescript"
  ]
}

To add support for React projects, add principled/react:

{
  "extends": [
    "principled/typescript",
    "principled/react"
  ]
}

To add support for Jest tests, add principled/jest:

{
  "extends": [
    "principled/typescript",
    "principled/jest"
  ]
}

You can also use React in your Jest tests:

{
  "extends": [
    "principled/typescript",
    "principled/react",
    "principled/jest"
  ]
}

Versioning

This project adheres to Semantic Versioning.

API

This project conforms to the specifications of an ESLint Shareable Config.

Contributing

This project is open for pull requests. Please refer to CONTRIBUTING.md for information about developing eslint-config-principled and submitting changes.

Issues

Please feel welcome to submit an issue for any problems or suggestions you may have regarding eslint-config-principled.

License

This project is licensed under the Unlicense. For the full license text, please see LICENSE.