AOT : "Supplied parameters do not match any signature of call target"
See original GitHub issueI’m submitting a …
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here
Current behavior When building with AOT, I got the error :
[at-loader] Checking finished with 26 errors Error in bail mode: [at-loader] compiled/node_modules/@swimlane/ngx-charts/release/bar-chart/bar-horizontal-2d.component.ngfactory.ts:784:35 TS2346: Supplied parameters do not match any signature of call target.
Please tell us about your environment: I’m using the AngularClass webpack seed
- ngx-charts version: 4.2.1
- Angular version: 2.4.6
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Supplied parameters do not match any signature of call target ...
On compiling this with AOT getting below error: PRINHYLTPAP0592:matata ajays$ ng build --prod --aot /myApp/src/$$_gendir/app/image-uploader/ ...
Read more >Supplied parameters do not match any signature of call target ...
When upgrade to angular 4 and angular\cli 1.0.0 getting this error when compiling with AOT: ERROR in ng:///C:/ProjentName/node_modules/angular2- ...
Read more >Supplied parameters do not match any signature of call target
Supplied parameters do not match any signature of call target. Quickest fix is to do const BodyAny:any = Body and use BodyAny ....
Read more >Angular2 AOT编译出现Supplied parameters do not match any ...
原因:函数调用时的参数与函数定义时的参数不匹配,如: go(path:string,param:s...,CodeAntenna技术文章技术问题代码片段及聚合.
Read more >报错Supplied parameters do not match any signature of call target_ ...
问题原因是html所绑定的方法与ts页面的方法参数不一致导致的.
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 FreeTop 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
Top GitHub Comments
Will this be resolved soon in a minor/patch release? Getting the same thing still using angular-cli with AoT (which no longer masks the warnings)
I confirm this with following versions:
Full error output: