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

@screamz/aurora

v1.0.0

Published

A set of configs and rules for Typescript projects.

Downloads

8

Readme

  • Prettier. Code formatter
  • Tslint. Typescript files linter

Installation and dependencies

Install dependencies using npm or yarn:

yarn add -D tslint prettier @screamz/aurora

Edit your package.json and add "prettier": "@screamz/aurora" to use the built-in prettier config.

Then chose your tslint config depending on your project type and add it to your tslint.json extends key:

  • Classic Typescript project such as NodeJS or Cloud Functions: @screamz/aurora/tslint-common
  • React project: @screamz/aurora/tslint-react

Good to go!

Good to know

Some rules are handled by Prettier and have been desactived in tslint to avoid conflicts thanks to both tslint-config-prettier & tslint-plugin-prettier.

Extending ?

  • If you want to extends the built-in Prettier config:

The package.json method does not offer a way to extend the configuration to overwrite some properties from the shared configuration. If you need to do that, import the file in a .prettierrc.js file and export the modifications, e.g:

module.exports = {
  ...require("@screamz/aurora"),
  semi: false
};
  • If you want to extends the tslint configuration

It's simple as adding rules in your tslint-config.json

{
  "extends": "@screamz/aurora/tslint-react",
  "rules": {
    "interface-name": false,
  }
}