Constructing ReconnectingWebsocket error in TypeScript
See original GitHub issueCode: new ReconnectingWebSocket(url)
Error: 'new' expression, whose target lacks a construct signature, implicitly has an 'any' type.'
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
reconnecting-websocket - npm
Start using reconnecting-websocket in your project by running `npm i ... TypeScript icon, indicating that this package has built-in type ...
Read more >Reconnecting a websocket in Angular and rxjs? - Stack Overflow
catch is doing is picking up any error produced in the block where the stream actually does receive some data. So adding the...
Read more >Reconnecting Websockets | Mike Polinowski
ReconnectingWebSocket : A small JavaScript library that decorates the WebSocket API to provide a WebSocket connection that will automatically reconnect if ...
Read more >Typescript (forked) - StackBlitz
Blank starter project for building TypeScript apps. ... import ReconnectingWebSocket from. 'reconnecting-websocket';. console.error(ReconnectingWebSocket).
Read more >'new' expression, whose target lacks a construct signature ...
I am using a bigint in my typescript package, however I can't seem to get typescript to recognise Bigint. The following code throws...
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
I get an error message, when using
"strict": true
in the compiler options:test.ts
:tsconfig.json
:Compile error:
If I remove
"strict": true
fromtsconfig.json
, the code compiles fine. But I want this option to betrue
.tsc: 2.4.2 reconnecting-websocket: 3.2.2
My understanding is that changing noImplicitAny in the library’s tsconfig will have no effect whatsoever when importing as only the importer project’s tsconfig will be in effect.