Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'never' has no compatible call signatures. #1219

Closed
arsyed04 opened this issue Jan 3, 2018 · 2 comments · Fixed by #1295

Comments

@arsyed04
Copy link

arsyed04 commented Jan 3, 2018

[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior
ERROR in node_modules/@swimlane/ngx-datatable/src/components/body/body.component.ts(406,19): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'never' has no compatible call signatures.

Expected behavior
No build error

Reproduction of the problem
ng serve or ng build

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

  • Table version: 0.8.x
    11.1.5

  • Angular version: 2.0.x
    5.1.2

  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

  • Language: [all | TypeScript X.X | ES6/7 | ES5]
    Typescript 2.7.0-dev.20171230
    ES5
    Angular Cli 1.6.3
@stewx stewx mentioned this issue Feb 5, 2018
9 tasks
@thomaswdean
Copy link

Is this being addressed? Just encountered this error yesterday and now I can't build with ng serve.

@esheleg
Copy link

esheleg commented Feb 15, 2018

Downgrade typescript to 2.6.2 solved the problem for me.
npm install typescript@2.6.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants