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

v1.1.1

Published

A bare bones, un-opinionated eslint config standard

Downloads

17

Readme

eslint-config-essentials

The bare bones, un-opinionated, essential - eslint config.

Philosophy

As a developer over the years I've always hated the fact that we just followed some standard without knowing why or how, we just follow it because the biggest dev houses do.

As I matured as a developer my overall vision for my career changed, and if there's one moral value that I stand for today is developer experience, and guess what? When it comes to linting, it's no different.

I've decided to write this config file, as something that will be a template for you to extend on and add your own rules that you / team feel are required as something that you will enjoy.

I don't believe in forcing my opinion on someone especially when it's a subjective matter on code style, and performance is not impacted. This not only stunts the other developer or everyone in your team, but it also makes me not enjoy developing, and the reason we're developers, is because we love what we do!

With that in mind I really hope, that this could serve as a helping base template for all your linting needs :)

Prerequisites

Peer dependencies

  1. "eslint": ">= 3"

Install

or

Usage

All you need to do is add the below prop to you eslint config file:

Example .eslintrc.js

Example .eslintrc.json file

Extending rules