Upgrading to Angular 10 + nebular 6 + Typescript 4.0.2 results in NbColumnDefDirective + NbTreeGridxxxxxDefDirective errors
See original GitHub issueIssue type
I’m submitting a … (check one with “x”)
- [ x ] bug report
- feature request
Issue description
Current behavior: Upgrading current project based on Angular 9 + nebular 5 to Angular10 + nebular 6 results in the following errors during compilation.
ERROR in node_modules/@nebular/theme/components/cdk/table/cell.d.ts:35:5 - error TS2610: ‘name’ is defined as an accessor in class ‘CdkColumnDef’, but is overridden here in ‘NbColumnDefDirective’ as an instance property.
35 name: string;
~~~~
node_modules/@nebular/theme/components/cdk/table/cell.d.ts:39:5 - error TS2610: 'stickyEnd' is defined as an accessor in class 'CdkColumnDef', but is overridden here in 'NbColumnDefDirective' as an instance property.
39 stickyEnd: boolean;
~~~~~~~~~
node_modules/@nebular/theme/components/tree-grid/tree-grid-def.component.d.ts:19:9 - error TS2611: 'columns' is defined as a property in class 'NbRowDefDirective<T>', but is overridden here in 'NbTreeGridRowDefDirective<T>' as an accessor.
19 set columns(value: Iterable<string>);
~~~~~~~
node_modules/@nebular/theme/components/tree-grid/tree-grid-def.component.d.ts:34:9 - error TS2611: 'columns' is defined as a property in class 'NbHeaderRowDefDirective', but is overridden here in 'NbTreeGridHeaderRowDefDirective' as an accessor.
34 set columns(value: Iterable<string>);
~~~~~~~
node_modules/@nebular/theme/components/tree-grid/tree-grid-def.component.d.ts:49:9 - error TS2611: 'columns' is defined as a property in class 'NbFooterRowDefDirective', but is overridden here in 'NbTreeGridFooterRowDefDirective' as an accessor.
49 set columns(value: Iterable<string>);
~~~~~~~
Expected behavior: Upgrade should work seamlessly.
Other information:
npm, node, OS, Browser
node -v v12.18.2
npm -v 6.14.7
Angular, Nebular
"@angular/animations": "^10.1.0",
"@angular/common": "^10.1.0",
"@angular/compiler": "^10.1.0",
"@angular/core": "^10.1.0",
"@angular/elements": "^10.1.0",
"@angular/flex-layout": "^10.0.0-beta.32",
"@angular/forms": "^10.1.0",
"@angular/google-maps": "^9.1.0",
"@angular/material": "^10.2.0",
"@angular/platform-browser": "^10.1.0",
"@angular/platform-browser-dynamic": "^10.1.0",
"@angular/router": "^10.1.0",
"@nebular/eva-icons": "^6.0.1",
"@nebular/moment": "^6.0.1",
"@nebular/security": "^6.0.1",
"@nebular/theme": "^6.0.1",
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Typescript version issue while upgrading to Angular 12
1 Answer 1 · There's no reference for typescript 4.5.4 in my code. I still ran uninstall command for it as you suggested....
Read more >Nebular - 3.5.0-4.0.0 Migration - GitHub Pages
The following migration steps are required to update: Update Angular to version 8 required; Update Nebular to version 4 required; Fix imports and...
Read more >Upgrading to Angular 10 + nebular 6 + Typescript 4.0.2 results ...
Current behavior: Upgrading current project based on Angular 9 + nebular 5 to Angular10 + nebular 6 results in the following errors during ......
Read more >@nebular/auth - npm
Start using @nebular/auth in your project by running `npm i ... TypeScript icon, indicating that this package has built-in type declarations.
Read more >Nebular meets Angular CDK
Nebular is an Angular library that simplifies complex rich UI applications ... The result was quite successful, and from our experiments, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same here. I had to downgrade my project’s typescript version from 4.0.2 to 3.9.7 as a workaround.
@yggg
Any plans to add support for Typescript 4.0.2?
Thanks