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

super-tslint

v1.0.9

Published

An extension of the tslint library that allows for watching files, adding better handling of multiple nested typescript projects and more human readable output.

Downloads

27

Readme

Super tslint

An extension of the tslint library adding the ability to watch files, better handle multiple nested tsconfigs, and more human readable output.

Installation

install the npm package

> npm i -g super-tslint

or if you prefer to install it locally

> npm i --save-dev super-tslint
> node ./node_modules/super-tslint/bin/super-tslint  ...

Usage

Flags

        -p, --project [path]    path to tsconfig, lints entire project.
        -q, --quote             a bit of inspiration.
        -h, --help              shows this dialog.

        --all                   lints all nested tsconfig.* projects.
        --fix                   auto fixes compatible errors.
        --watch                 watches files for on save and re-runs linter.

Lint a project

> super-tslint --project example/project-a/tsconfig.json

Lint a single file

> super-tslint path/to/file.ts

Lint and auto fix a project

> super-tslint --fix --project example/project-a/tsconfig.json

Lint all nested tsconfigs

this will lint all ts projects nested from the current directory

> super-tslint --all

Lint and watch for changes

> super-tslint --watch --project example/project-a/tsconfig.json

Lint and watch all

> super-tslint --watch --all

Inspire yourself to write better code

> super-tslint --quote

Setting up multiple tsconfigs

For the following example, lets say we have the below project structure

|____projects
|   |__proj-a
|   |  |__file-a.ts
|   |  |__tsconfig.json
|   |
|   |__proj-b
|   |  |__file-b.ts
|   |  |__tsconfig.json
|   |
|   |__tslint.json
|
|__tslint.json

In the root tslint.json, define your general rules for the entire repo. You can also choose to include or exclude certain file globs here.

{
  "extends": "tslint:recommended",
  "rules": {}
}

In the projects/tslint.json, you can extend the root config and make changes to your specific nested files. Tslint will always use the closest tslint.json as it's ruleset.

{
  "extends": "../tslint.json",
  "rules": {
    "member-access": false,
    "no-console": {
      "severity": "warning"
    }
  },
  "linterOptions": {
    "exclude": [
      "**/typings/**"
    ]
  }
}

An example tsconfig.json

{
  "compilerOptions": {
      "alwaysStrict": true,
      "noImplicitAny": true,
      "removeComments": true,
      "preserveConstEnums": true,
      "outFile": "proj-a-bundle.js",
      "sourceMap": true
  },
  "exclude": [
      "node_modules",
      "**/*.spec.ts"
  ]
}

And then to lint all nested projects run

> super-tslint --all

which could produce the following example output

C:/root/projects/proj-a/file-a.ts:10:16
ERROR: 10:16            semicolon                Missing semicolon
WARNING: 14:5            no-console             Calls to 'console.log' are not allowed.
ERROR: 14:17            quotemark                ' should be "

C:/root/projects/proj-b/file-b.ts:10:16
ERROR: 10:16            semicolon                Missing semicolon


TOTAL ERRORS:     3
TOTAL WARNINGS:   1

Exit codes

If any error occurs during linting, process will return exit status 1 (this does not include warnings).

Example output coloring