angular-eslint
Monorepo for all the tooling related to using ESLint with Angular
MIT License
Bot releases are hidden (Show)
14.0.0 (2022-06-23)
As always we recommend that you update your existing workspaces by using ng update as we provide some helpful schematics to help migrate your workspaces to the latest and greatest. Running the following will update Angular, the Angular CLI and angular-eslint together:
ng update @angular/core @angular/cli @angular-eslint/schematics
BREAKING CHANGES
This is a major version bump and comes with some breaking changes, one of which might possibly impact your ESLint configuration if you are targeting inline HTML templates with a very specific glob pattern because the virtual filename has changed (read on to learn more).
-
update Angular to v14
- All packages now require the use of Angular CLI >= 14.0.0 < 15.0.0
-
dropped support for Node 12 (in alignment with Angular's own version policy)
-
extracted inline HTML templates now contain the original Component filename in their processed virtual filename
- When ESLint runs on your Component files, if you are using the recommended configuration, it will invoke a processor we have set up to extract the inline HTML templates from your Component declarations. Behind the scenes we give these extracted templates virtual filenames ending in
.htmlso that rules targeting HTML files can also target your inline templates. -
Before: In v13 the filename looked like this:
inline-template-${++i}.component.html, whereiwas an incrementing integer (in case for example you had multiple Component declarations in the same.tsfile. -
Now: In v14 the filename now looks like this
inline-template-${baseFilename}-${++i}.component.html, whereihas the same incrementing integer behavior as before, but we now include the base filename within the virtual filename.- E.g. if you have a test file in
projects/foo/src/app/app.spec.tswhich declares a Component with an inline template, the virtual filename generated behind the scene for that template will beinline-template-app.spec.ts-1.component.html. - This new behavior allows you to use ESLint overrides to apply different behavior to Component inline templates in different files.
- E.g. if you have a test file in
- When ESLint runs on your Component files, if you are using the recommended configuration, it will invoke a processor we have set up to extract the inline HTML templates from your Component declarations. Behind the scenes we give these extracted templates virtual filenames ending in
Features
- update eslint to
^8.18.0(automatically migrated viang update) - update typescript-eslint to
^5.29.0(automatically migrated viang update) - update deprecated
cli.defaultCollectionusage inangular.jsonto usecli.schematicCollectionsinstead (automatically migrated viang update)
13.0.0 (2021-11-18)
Whilst this is a major release of the packages, in this case the major version change is primarily there to signify alignment with v13 of Angular.
You should look to migrate to v13 of all Angular packages, as well as v8 of eslint and v5 of typescript-eslint.
All of this will be handled for you automatically if you leverage the ng update schematics provided by @angular-eslint. You can simply include @angular-eslint/schematics in your ng update command alongside @angular/cli and @angular/core, for example:
npx ng update @angular/cli @angular/core @angular-eslint/schematics
12.6.0 (2021-10-25)
Bug Fixes
- eslint-plugin: [sort-ngmodule-metadata-arrays] remove the property restriction (#694) (440f6dc)
- eslint-plugin: [sort-ngmodule-metadata-arrays] report the correct node (#693) (886db08)
- eslint-plugin: more appropriate language for no-attribute-decorator (#696) (4dde82c)
-
eslint-plugin-template: [i18n] ignore empty strings and non-texts within
BoundTextby default (#683) (4075643)
Features
12.4.0 (2021-09-09)
Bug Fixes
- eslint-plugin: [no-empty-lifecycle-method] incorrect suggestions and correct reports (#606) (a446e8f)
- eslint-plugin: [sort-ngmodule-metadata-arrays] handle literal metadata and computed properties (#667) (f993069)
- eslint-plugin: properly handle computed literals for some rules (#600) (fbd6ff7)
- eslint-plugin-template: [i18n] fixes some incorrect reports (#665) (a011b9d)
-
eslint-plugin-template: [no-call-expression]:
FunctionCalls not being reported (#601) (5552b13) -
eslint-plugin-template: include more checks for
isHiddenFromScreenReader(#545) (db2bc05)
Features
12.3.0 (2021-07-13)
Bug Fixes
-
eslint-plugin: [no-input-prefix] handle alias and
inputsmetadata property (#582) (675ee11) -
eslint-plugin: [no-input-rename] handle alias and
inputsmetadata property (#583) (2883e18) -
eslint-plugin: [use-component-view-encapsulation] handle literal
encapsulationproperly (#586) (3a9b7f4) - eslint-plugin: [use-pipe-transform-interface] handle type imports properly in fix (#592) (ac3fb12)
Features
- builder: add noEslintrc option (#588) (4b150bf)
- builder: add resolvePluginsRelativeTo option (#590) (3bea308)
- builder: add rulesdir option (#589) (ff9557d)
- builder: added outputFile option (#587) (420734b)
- eslint-plugin: [component-selector] handle shadow dom components properly (#559) (ecbe684)
- eslint-plugin: [no-pipe-impure] add suggestion (#585) (149bf2f)
- schematics: better support @angular/cli 12.1 (#591) (c5da07b)