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

@okp4/eslint-config

v2.0.0

Published

ESLint shareable config used @okp4.com

Downloads

55

Readme

eslint-config

ESLint shareable config used @OKP4

lint build conventional commits contributor covenant License

Purpose & Philosophy

This repository holds the shared ESLint configuration used for all our TypeScript projects at OKP4.

The current configuration enforces strict dogmatic rules - (too strict you might think)- in addition to those recommended by the various linting extensions available such as ESLint itself, and various plugins such as react, react-hooks, typescript-eslint...

Indeed, at OKP4 we are convinced that the quality of the code depends on clear and consistent coding conventions, with an automated enforcement.

The rules configured are mainly based on two pillars:

  • React: We encourage as much as possible an architectural approach focusing on Functional Components. That's why we enforce a strict mode and a High Severity according to the recommendations of Facebook Core (React Team).
  • TypeScript: At OKP4, we love Type Safety, and we are deeply conviced that better type safety means less error in production. That's one of the reasons we chose TypeScript over JavaScript. We've therefore adopted very strict Type Checking rules in order to take advantage of the best of TypeScript.

Installation

NPM

npm version must be at least equal to 7.0.0 to install automatically peer-dependencies (see https://github.blog/2020-10-13-presenting-v7-0-0-of-the-npm-cli/)

npm i @okp4/eslint-config

Yarn

If you want to use yarn, you must first list all peer dependencies using npm and add then individually with yarn.

First, list the peer dependencies and versions:

npm info @okp4/eslint-config@latest peerDependencies

Then run the following command line for each listed peer dependency.

yarn add --dev <dependency>@<version>

Usage

ESLint

Create your .eslintrc configuration file, taking care to properly inform the source of the project used for the TypeScript parser:

{
  "extends": "@okp4", // may be combined with other shareable configurations
  "parserOptions": {
    "project": "./tsconfig.json"
  }
}

Prettier

Cretate your .prettierrc.js configuration file :

module.exports = {
  ...require('@okp4/eslint-config/.prettierrc.js')
}

Contributing

So you want to contribute? Great. We appreciate any help you're willing to give. Don't hesitate to open issues and/or submit pull requests.

Remember that this is the configuration we use at OKP4, and that we apply everywhere in our private and public projects. This is why we may have to refuse change requests simply because they do not comply with our internal requirements, and not because they are not relevant.