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

@pxlwidgets/eslint-config-angular

v17.0.1

Published

The Angular extension for our ESLint configuration base.

Downloads

72

Readme

ESLint configuration - Angular

npm version

The Angular extension for our ESLint configuration base. This configuration was migrated from another repository and was previously published as a special configuration under @pxlwidgets/eslint-config.

Table of contents

[[TOC]]

Peer dependencies

About

This repository maintains distinct branches for each major Angular version. By default, the two latest versions are actively supported. The branch names follow the angular-{MAJOR_VERSION} pattern, and each have their own package version tags within that major version of Angular. Therefore, they also all have their own CHANGELOG history.

Version tags are for each branch in sync with its corresponding Angular version. For instance, branch angular-12 will have version release tags that all follow the pattern v12.<minor>.<patch>. Therefore, breaking changes may occur in minor version updates of this package. You may consult the CHANGELOG file in the respective branch to check for any breaking changes.

Installation

Please refer to one of the following branches for exact installation instructions based on your Angular version. If you use an Angular version that is older than any version listed, please try to update your project so that it can use any of these configuration versions. If you can not update then file an issue, and refer to your project there.

View installation instructions for:

Usage

Angular uses the ng lint command. In order to make that command use ESLint instead of TSLint, follow this guide , or update the projects > app > architect > lint path in your angular.json file as follows:

{
  "lint": {
    "builder": "@angular-eslint/builder:lint",
    "options": {
      "lintFilePatterns": [
        "src/**/*.ts",
        "src/**/*.html"
      ]
    }
  }
}

Note that the angular-eslint package will only work for Angular 8+. There is also a separate configuration for E2E in the angular.json if you are using Angular's default E2E testing you may need to make sure that the linting config for it is set up similarly to the main build.

Development

  • For each new Angular version create a new branch angular-{MAJOR_VERSION}, e.g. angular-12, and sync the dependency versions in that branch. All @angular-eslint/* dependencies also sync their major versions with the compatible Angular version.

  • Maintain a tag sequence for each major Angular version independently, and only create tags for Angular version x in the corresponding branch angular-x.

  • Don't merge version branches into base.

  • When an update to the generic documentation is required, perform this update in base, and merge base into all angular-x branches.

  • When an update to the generic ESLint configuration is required, perform this update in base, and merge base into as many angular-x branches as possible. When you do, make sure that the configuration update is compatible with the ESLint version required by the target branch. You can check the required version by checking out the target branch and then running npm install && npm ls eslint.

  • Since tags for specific configuration versions are created on angular-x branches, never rebase any of these branches.