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

@silvercar/js-constable

v1.2.0

Published

Silvercar's JavaScript/TypeScript ESLint Config

Downloads

339

Readme

JS Constable

Javascript/Typescript rules to ~~code~~ live by

JS Constable logo

Table of Contents

Background

The goal of this project is to not only get clean code, but also a more uniformly-formatted codebase to help devs more easily move between projects, especially in a siloed multi-team product development department.

These linting rules are largely derived from Airbnb's Javascript Style Guide with some minor modifications mostly related to strictness (such as warning instead of errors) for the sake of development speed. Much of the linting rules are covered in-depth in in the Airbnb Style Guide.

Installation

npm install @silvercar/js-constable --save-dev

Recommended Usage

This is intended to serve as a general guideline for ESLint throughout Silvercar projects wherever JS/TS is concerned. If you need to change linting rules, go ahead, but please consider contributing it back to this repo so that other projects may benefit.

Add this lint script within package.json (assuming code to lint is inside a src/ folder):

"scripts": {
  "lint": "eslint src/**/*.js src/**/*.jsx src/**/*.ts src/**/*.tsx"
},

Easily lint your project manually via npm run lint.

Most IDEs should automatically pick up an .eslintrc and begin to automatically lint your code on-save or similar, but note that sometimes additional IDE-specific configuration might be needed such as this example.

Make sure to include a proper .eslintignore file to avoid long linting times.

React

Add to .eslintrc for Typescript:

{
  "extends": "./node_modules/@silvercar/js-constable/react-ts"
}

FAQ

  • But but but, TSLint?!
  • Will Markdown code blocks also be linted?
    • Yes, only if you use js, javascript, jsx, or node in your fenced code blocks
    • This will be linted:
      ```js
      const myFirstAddend = 1;
      const mySecondAddend = 2;
      
      const mySum = myFirstAddend + mySecondAddend;
      console.log(mySum));
      ```
    • This can be prevented by using <!-- eslint-skip --> above those same code blocks

License