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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@medienwerft/eslint-config-angular

v0.1.7

Published

Default angular configuration for eslint.

Readme

eslint configuration for angular

To ensure a high and consistent code quality for .ts, .js, .html we use eslint.

This eslint extends the ruling conventions from angular linting and prettier. Therefore, you must have prettier installed in your project.

To check the rules see .eslintrc.json. If for some reason a rule doesn't fit your project, you can override the specific rule in the .eslintrc.json (as demonstrated below) of your project.

Installing @medienwerft/eslint-config-angular package

npm install @medienwerft/eslint-config-angular prettier --save-dev

Create config

1- run ng add @angular-eslint/schematics to add linting to your angular project and create the .eslintrc.json automatically

2- add the following to your .eslintrc.json file:

{
    "extends": ["@medienwerft/eslint-config-angular/.eslintrc"]
}

Use

run lint over the whole project:

ng lint

run and fix code:

ng lint --fix

adding eslint to lintstagedrc

{
  "*{.ts,.js,.html}": "eslint --fix",
  ... other lint staged commands,
}