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

@plntr/eslint-config

v1.9.0

Published

Planitar eslint configuration

Downloads

52

Readme

eslint-config-plntr

This package provides Planitar's .eslintrc as an extensible shared config. This config should be used in any JS project developed by Planitar.

The package follows Planitar's JS code conventions and is built on top of Airbnb's eslint config.

Usage

Three ESLint configurations are provided:

  • esm is an ES6+ configuration.
  • es5 is an ES5 configuration.
  • react-jsx is a React specific configuration.
  • vue is a Vue specific configuration.

All three ESLint configurations listed above come in 2 variations:

  • a strict and unforgiving configuration that should be used before code is committed or deployed to production.
  • a more relaxed configuration where syntactic rules are set to warning level, that can be used in dev environment; prefixed with -dev.

List of provided configurations:

| Type | "extends" path | Description | |---|---|---| | ES6+ | plntr/esm | strict esm config | | | plntr/esm-dev | relaxed esm config | | React JSX | plntr/react-jsx | strict react-jsx config | | | plntr/react-jsx-dev | relaxed react-jsx config | | Vue | plntr/vue | strict vue config | | | plntr/vue-dev | relaxed vue config | | Jest | plntr/jest | strict jest config | | | plntr/jest-dev | relaxed jest config | | Typescript | plntr/typescript | strict typescript config | | | plntr/typescript-dev | relaxed typescript config | | ES5 | plntr/es5 | strict es5 config | | | plntr/es5-dev | relaxed es5 config |

In order to use any of the configs just add "extends": "<IMPORT PATH>" to your eslintrc.* file. For example, if you want to use React JSX rules, add "extends": "react-jsx".

By default if you just import the package, "extends": "plntr", a strict esm config is used.

Note: eslint documentation mentions:

A sharable configuration is an npm package that exports a configuration object. Make sure the package has been installed to a directory where ESLint can require it.

The extends property value can omit the eslint-config- prefix of the package name.

Since the package name is eslint-config-plntr, when it is used in extends property the prefix can be omitted, hence the "extends" paths listed above all use plntr instead of eslint-config-plntr.