NOT SUPPORTED: keyword "id", use "$id" for schema ID : TSLint (ng add @angular-eslint/schematics)

Question

I am upgrading my Angular 10 application to Angular 13. I did well with other compatibilities of dependencies. The project is compiling and working fine. Now the time for TSLint I tried to update the lint with the below command.

ng add @angular-eslint/schematics

But getting the error message:

An unhandled exception occurred: NOT SUPPORTED: keyword "id", use "$id" for schema ID

angular-eslint does not have a stable version which supports Angular 13 yet, see this GitHub issue: https://github.com/angular-eslint/angular-eslint/issues/790 — JSON Derulo, Nov 09 '21 at 10:31
I've been running into same issues with same versions today (v10 to v13). So far I've got it to install by deleting package lock and node_modules then running ng add @angular-eslint/schematics@next — cvb, Nov 09 '21 at 22:13

score 29 · Answer 1 · edited Jun 02 '23 at 23:00

29

For eslint:

ng add @angular-eslint/schematics@12 #for angular 12

ng add @angular-eslint/schematics@13 #for angular 13

ng add @angular-eslint/schematics@14 #for angular 14

edited Jun 02 '23 at 23:00

BuZZ-dEE

6,075
12
66
96

answered Dec 04 '22 at 00:02

ilkerdev

301
3
4

2

You can specify more, with `@14.2.0`, for example, these days. (but `@14.2.10` will be excessive: it won't match at this level of detail). – Marc Le Bihan Dec 25 '22 at 10:43

score 25 · Answer 2 · edited Nov 10 '21 at 07:38

25

ng add @angular-eslint/schematics@next

This worked for me github.com/angular-eslint/angular-eslint/issues/790.

edited Nov 10 '21 at 07:38

Chris Claude

973
12
25

answered Nov 09 '21 at 15:42

Yoandri Garcia

251
2
3

2

This worked for me when upgrading to Angular 14. Thanks! – Jared Jun 05 '22 at 13:53

score 11 · Answer 3 · answered Dec 14 '21 at 20:01

11

I solved the problem downgrading angular cli version to 12

answered Dec 14 '21 at 20:01

Richard Aguirre

543
6
14

score 8 · Answer 4 · answered Dec 19 '21 at 05:07

8

It seams that a lot of packages throw this error. I had the same error when adding NgRx store. It looks like that installing the latest version of the packages usually fix the issue:

ng add package_name/@latest

answered Dec 19 '21 at 05:07

NeNaD

18,172
8
47
89

1

Thanks, this worked for me with @angular/pwa: ```ng add @angular/pwa@latest --project MyProjectName```. The project is using Angular 14. – cjs1978 Feb 01 '23 at 07:43

score 3 · Answer 5 · answered Dec 18 '21 at 17:25

3

I had the same problem. I could fix it by by upgrading angular/universal to the same version as my angular version is.

answered Dec 18 '21 at 17:25

pubkey

617
8
17

Ketan · Answer 6 · 2022-09-02T10:14:00.023

3

I faced the same issue in Angular 14, IONIC 6 project while generating pages/components . And resolved it by replacing id with $id manually on following paths:

node_modules > @Ionic > angular-toolkit > schematics > page > schema.json > replace id with $id on line 3.
node_modules > @Ionic > angular-toolkit > schematics > component > schema.json > replace id with $id on line 3.

edited Sep 02 '22 at 10:14

answered Sep 02 '22 at 10:10

Ketan

31
3

3

doing `npm i @ionic/angular-toolkit@latest --save-dev` solved this for me with angular@16 and Ionic@6 – babycakes Oct 12 '22 at 14:27

score 3 · Answer 7 · answered Dec 21 '22 at 21:39

3

For me, just by adding the most current version, did it:

ng add @angular/pwa@15.0.4

The list of versions are here available.

answered Dec 21 '22 at 21:39

Walter Fuchs

167
2
11

score 2 · Answer 8 · answered Nov 20 '22 at 16:50

2

It appear while I'm using angular 14, after upgrading angular 15(before that reinstalling angular cli) resolve problem for me.

answered Nov 20 '22 at 16:50

Azhar

693
9
22

score 1 · Answer 9 · answered Nov 24 '22 at 23:43

1

Install manually the version of @angular/pwa corresponding to your version of angular and then run "ng add @angular/pwa"

answered Nov 24 '22 at 23:43

Xilerth

11
1

score 0 · Answer 10 · answered Mar 24 '22 at 12:55

I had a conflict where the third-party package I was using had been replaced by an official one, but for some reason I had both of them in my package.json file The real issue though was that the angular.json file was using the older builder instead of the newer one. I removed the package and used ng add to add the new package via its schematic, and after that things started working properly.

score 0 · Answer 11 · answered May 22 '23 at 19:48

Check if your versions match ng version

Mine was:

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1100.5
@angular-devkit/build-angular   15.2.8
@angular-devkit/core            11.0.5
@angular-devkit/schematics      15.2.8 (cli-only)
@angular/cli                    15.2.8
@nguniversal/builders           11.0.1
@nguniversal/express-engine     15.2.1
@schematics/angular             15.2.8 (cli-only)
rxjs                            7.5.0
typescript                      4.9.5

So you see, @angular-devkit/architect needed to be 0.15 and @nguniversal/builders needed to be on 15 as well in my case.

From this github post:

Remove your node_modules and delete your lock file and rebuild it with a fresh install
Force clean your global npm cache (npm clear cache --force)
delete your npx cache (on a mac that is rm -rf ~/.npm/_npx)

The first step was sufficient for me.

NOT SUPPORTED: keyword "id", use "$id" for schema ID : TSLint (ng add @angular-eslint/schematics)

11 Answers11

Linked