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

@strut-software/eslint-config

v1.8.6

Published

An opinionated collection of ESLint configs to be used across Strut and Rithm projects

Downloads

5

Readme

Lint Rules

Description

This package contains a set of ESLint configs to be used across Strut Software Solutions projects and Rithm Software projects. This is to ensure each project has the same set of rules to keep projects consistent.

Configs

Config files exist for the following use cases and are summarized below. You can mix and match these as needed and several configs inherit other configs automatically.

  • javascript - Recommended rules for projects using JavaScript.
  • typescript - Recommended rules for projects using TypeScript.
    • Includes and modifies the rules from javascript as TypeScript is a superset of JavaScript.
  • angular - Recommended rules for projects using Angular.
    • Includes and modifies the rules from typescript and rxjs as Angular uses TypeScript and RxJS by default.
  • angular-html - Recommended template (HTML) rules for projects using Angular.
    • Used in conjunction with @angular-eslint/template-parser.
  • rxjs - Recommended rules for projects using the RxJS library.

Installation

From the root folder of your project, install the package with the following command:

npm i @strut-software/eslint-config --save-dev

Usage

Once the package is installed, add the desired configs to the "extends" section of the eslintrc.json in the root of your project:

{
    "root": true,
    "ignorePatterns": [
        "projects/**/*"
    ],
    "overrides": [
        {
            "files": [
                "*.ts"
            ],
            "parserOptions": {
                "project": [
                    "tsconfig.json"
                ],
                "createDefaultProgram": true
            },
            "extends": [
                "@strut-software/eslint-config/angular"
            ],
            ...
        }
        ...
    ]
}

Afterwards, you will be able to run your desired lint command to use the newly-imported lint rules.

NOTE: Keeping this package up to date is highly recommended. Be sure that the version number in your package.json contains a ^ before the version number to update to the newest minor version when using npm update.

Example:

"devDependencies": {
    ...
    "@strut-software/eslint-config": "^1.1.0",
    ...
}

Package maintenance

Uses a token from NPM as a github secret - this secret is stored in the org level.