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

ng2lint

v0.0.10

Published

A set of linters for Angular 2 applications, following https://github.com/mgechev/angular2-style-guide.

Downloads

42

Readme

ng2lint

A set of tslint rules for static code analysis of Angular 2 TypeScript projects.

Recommended configuration

Below you can find a recommended configuration which is based on the Angular 2 Style Guide.

{
  "directive-selector-name": [true, "camelCase"],
  "component-selector-name": [true, "kebab-case"],
  "directive-selector-type": [true, "attribute"],
  "component-selector-type": [true, "element"],
  "directive-selector-prefix": [true, "sg"],
  "component-selector-prefix": [true, "sg"],
  "host-parameter-decorator": true,
  "input-parameter-decorator": true,
  "output-parameter-decorator": true,
  "attribute-parameter-decorator":true,
  "input-property-directive":true,
  "output-property-directive":true
}

Roadmap

  • [x] Directive selector type.
  • [x] Directive selector name convention.
  • [x] Directive selector name prefix.
  • [x] Component selector type.
  • [x] Component selector name convention.
  • [x] Component selector name prefix.
  • [x] Use @Input instead of inputs decorator property.
  • [x] Use @Output instead of outputs decorator property.
  • [x] Use @HostListeners and @HostBindings instead of host decorator property.
  • [ ] Do not use nativeElement injected with ElementRef.
  • [x] Do not rename inputs.
  • [x] Do not rename outputs.
  • [ ] Externalize template above n lines of code.
  • [x] Do not use the @Attribute decorator.
  • [ ] Do not use forwardRef.
  • [ ] Rise a warning for impure pipes.
  • [ ] Do not declare global providers.
  • [ ] Follow convention for naming the routes.
  • [ ] Use @Injectable instead of @Inject.
  • [ ] Single export per module, except facade modules.
  • [ ] Proper naming of modules (kebab-case followed by module type followed by extension for regular modules, module name plus extension name for facades).
  • [ ] Verify if used directive is declared in the current component or any parent component.
  • [ ] Verify that property or method used in the template exists in the current context.
  • [ ] Proper naming of directives and components (name plus (Directive|Component) suffix).
  • [ ] Locate component templates in the same directory.
  • [ ] Locate tests in the same directory (rise optional warning when no test file is found).
  • [ ] Rise warning on complex logic inside of the templates.
  • [ ] Do not manipulate elements referenced within the template.
  • [ ] Implement life-cycle hooks explicitly.
  • [ ] Implement Pipe transform interface for pipes.
  • [ ] Proper naming for pipes (kebab-case, optionally prefixed).

License

MIT