Compilation error after adding nebular to angular 10 app
See original GitHub issueI get an error after adding the Nebular theme to my angular app with the schematic command ng add @nebular/theme
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>);
~~~~~~~
Here is my system and CLI configuration
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 10.1.0
Node: 12.18.2
OS: darwin x64
Angular: 10.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.1001.0
@angular-devkit/build-angular 0.1001.0
@angular-devkit/build-optimizer 0.1001.0
@angular-devkit/build-webpack 0.1001.0
@angular-devkit/core 10.1.0
@angular-devkit/schematics 10.1.0
@angular/cdk 10.2.0
@ngtools/webpack 10.1.0
@schematics/angular 10.1.0
@schematics/update 0.1001.0
rxjs 6.6.2
typescript 4.0.2
webpack 4.44.1
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Unable to find the np-install for nebular - Stack Overflow
Can someone tell me which nebular module I need to install to fix this? Failed to compile. ./src/styles.scss (./node_modules/@angular-devkit/ ...
Read more >Install Nebular - GitHub Pages
Using Angular CLI. Installation. We strongly recommend developing Angular applications with @angular/cli . To install it use the following command:
Read more >NG0201: No provider for {token} found! - Angular
You see this error when you try to inject a service but have not declared a corresponding provider. A provider is a mapping...
Read more >How To Solve The Schematic Workflow Failed Error In Angular
js and vs code and then runs a command on cmd/terminal “npm install –g @angular/CLI”, then creates a project using the command “ng...
Read more >ngx-echarts - npm
Start using ngx-echarts in your project by running `npm i ngx-echarts`. ... Angular >= 13; v7.x for Angular >= 11; v6.x for Angular...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
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
For those, who need a hotfix, add this to
tsconfig.json
:I got the same errors. I just came to add the new issue but saw you already had this added.
The current workaround is:
Downgrade the typescript and tslint versions.
But I am not sure this will work in the future
Thanks.