Monorepo for all the tooling related to using ESLint with Angular
MIT License
Bot releases are hidden (Show)
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
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
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
.html
so that rules targeting HTML files can also target your inline templates.inline-template-${++i}.component.html
, where i
was an incrementing integer (in case for example you had multiple Component declarations in the same .ts
file.inline-template-${baseFilename}-${++i}.component.html
, where i
has the same incrementing integer behavior as before, but we now include the base filename within the virtual filename.
projects/foo/src/app/app.spec.ts
which declares a Component with an inline template, the virtual filename generated behind the scene for that template will be inline-template-app.spec.ts-1.component.html
.^8.18.0
(automatically migrated via ng update
)^5.29.0
(automatically migrated via ng update
)cli.defaultCollection
usage in angular.json
to use cli.schematicCollections
instead (automatically migrated via ng update
)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
BoundText
by default (#683) (4075643)FunctionCall
s not being reported (#601) (5552b13)isHiddenFromScreenReader
(#545) (db2bc05)inputs
metadata property (#582) (675ee11)inputs
metadata property (#583) (2883e18)encapsulation
properly (#586) (3a9b7f4)