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

pgs-dev-tslint

v10.1.3

Published

PGS tslint rules

Downloads

21

Readme

alt text

PGS-dev-tslint

PGS standard tslint rules.

tslint.json file contains general rules for any TypeScript project.

tslint-rxjs.json file contains general rules for any TypeScript project with RxJS.

tslint-angular.json file contains general rules for any angular projects.

Optional rules

interface-name - forces interfaces to start with "I" prefix. It helps in some situations but it's not mandatory.

no-string-literal - there might be an issue with testing private methods etc.

object-literal-sort-keys - nice to have, but no auto fix -> time consuming

trailing-comma - can be set as the cfg below if you don't like trailing commas.

{
  true,
  {
    "multiline": "never",
    "singleline": "never"
  }
}

naming-convention - can be slightly adjusted per project depending on devs preferences

member-access - might be set to true if devs agree to always write "public" member access

whitespace - can be adjusted depending on devs preferences

How to use

Verify which version you need from the 3 versions available (tslint.json, tslint-rxjs.json, tslint-angular.json)

Update your project tslint.json to extend rules from the previously selected file.

Update tslint.json rules to overwrite optional official rules or add unofficial ones if needed.