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

tslint-config-unional

v0.10.0

Published

tslint config that follows uninoal/typescript style guide

Downloads

18,338

Readme

tslint-config-unional

NPM version NPM downloads Build status

Greenkeeper Semantic Release

Stories in Ready Visual Studio Code

A tslint extension package with several styles to choose from.

Design Principles

There are several configurations available in this package. Although they are different as they are designed for different programers, here are the principles that they all follows:

  • They are designed to be used by team
  • Each team member can use their own IDE of choice
  • The formatter available on each IDE should work with each configuration
  • Code should look well and consistent on each IDE with folding
    • so that when you stop by your team member's cube, the code looks the same.
    • i.e., unfortunately, no [tab]
  • Thrive for easy to write (with fewest keystrokes) while keeping the code clean

Usage

# Install
npm install tslint-config-unional
// tslint.json
{
  "extends": "tslint-config-unional" // or other styles
}

About Supported IDE

Within this project, I use the term IDE and editor interchangably in this context. The line between IDE and editor is burring by the day anyway.

I list the IDEs supported for specific style that I or some collaborators have verified. If your IDE of choice is not listed, it doesn't necessary mean the style doesn't work on your IDE.

Feel free to try it out, and let me know if it works for you or not so that I can update the list accordingly. Also, the best thing to do and file issues on your IDE so that you can use the style that you like.

Styles

Versioning

  • patch loosen rules and will not cause build to fail.
  • minor not used as adding rules will likely cause build to fail.
  • major adding rules or adding new styles, or making rule more strict then before.

LICENSE

MIT