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

v3.0.3-beta

Published

Custom eslint configurations

Downloads

15

Readme

eslint-config-hjcostabr76

Custom eslint configurations designed for typescript developing.

It's good for:

  • nodejs;
  • React JS;

It Will be good for (soon):

  • React Native;

Table of Contents

Principles

  1. Type Safety:

    Typescript is powerfull and awesome! Let's make it work for us!

  2. Less is more:

    We should write less. Less code means less places where a bug might emerge from. So whenever you can make it smaller and cleaner do It! (As far as it doesn't overrule principle #1).

  3. S.O.L.I.D. and Clean Code:

    Well, you know about it. Right?

How to

  • Installation:

    $ npm i -D eslint-config-hjcostabr76
  • Other dependencies:

    To use it you'll need ESLint Typescript parser and, ESLint packages to be installed.

  • Config file:

    With that all set you'll only need to build your project's eslint config file. It should look something like this:

    // .eslintrs.js
    
    module.exports = {
        parserOptions: {
            project: './tsconfig.json',
            tsconfigRootDir: __dirname,
        },
        extends: [
            'hjcostabr76/ts-node'
        ],
    
        ...
    }

Sub-packages

You can simply import it into your lint config. If you do this you will be getting general typescript rules only. All other configs derive from it (except spellcheck).


// .eslintrs.js

module.exports = {
    
    ...
    
    extends: 'hjcostabr76',

    ...
}

But what you probably want to do is to get some sub package(s). They are:

  • ts-node: Rules for NodeJS with typescript;
  • ts-package: Rules for writing your npm packages using typescript;
  • tsx: React with Typescript;
  • spellcheck: No need for description;

So your eslint config might come to look more like:


// .eslintrs.js

module.exports = {
    
    ...
    
    extends: [
        'hjcostabr76/ts-node',
        'hjcostabr76/spellcheck',
    ],

    ...
}

Soon there will be more sub packages for React

Used Plugins

This set of rules was built thanks to some good plugins presented by the community: