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

@grammarly/tslint-config

v0.6.0

Published

TSLint configuration for Grammarly TypeScript projects

Downloads

25

Readme

grammarly-tslint-config

This repository contains a configuration for TSLint that is shared between our TypeScript projects. This configuration can be considered a recommended set of rules for any TypeScript project. However, you can still extend this configuration (see this article) for custom, per-project settings.

Apart from built-in set of rules (see more docs here), we also use some third-party TSLint rules:

We have also implemented a couple of custom rules.

Usage

Install in a new project:

$ yarn add typescript tslint @grammarly/tslint-config
$ cp ./node_modules/@grammarly/tslint-config/default-tslint.json ./tslint.json

OR

$ npm i -D typescript tslint @grammarly/tslint-config
$ cp ./node_modules/@grammarly/tslint-config/default-tslint.json ./tslint.json

Use:

$ ./node_modules/bin/tslint ./src/**/*.ts*

Or in an npm script:

{
  ...
  "scripts": {
    "lint": "tslint ./src/**/*.ts*"
  }
  ...
}

It is also recommended to run TSLint on every build, so you can detect and fix problems earlier:

{
  ...
  "scripts": {
    "build": "tsc && tslint ./src/**/*.ts*"
  }
  ...
}

Contributing

As usual, pull-requests are welcome. Constructive discussions are welcome too. If you want to discuss, add or change this configuration, please file an issue.