Closed dthevenin closed 3 years ago
Adding #@types/long" in my project dependencies did fix the issue. I will close this PR that does not make sense anymore.
Maybe you could document that dependencies for typescript users.
@dthevenin @types/long
is a dev dependency? I'm not sure if that's the right place. Not using TS.
@dthevenin
@types/long
is a dev dependency? I'm not sure if that's the right place. Not using TS.
@michaelwittig
somehow my TS project fail to compile with the module node-q
. I found 2 solutions to fix the issue (actually I did not investigate the real root cause):
long
in node-q
: that PR (but I forget the remove the dependency in the package.json).@types/long
in my project; which I should not do since I'm not using it (but in the time being it's ok).I think at the end, since the project seems to work without using the type long
, we should remove it.
But I don't Know why we have that at the first place.
Do you remember the rational behind that dependency?
A q long can not always be represented as a JS Number.
From the README:
5: You can disable long2number deserialization during connect(params, cb) to represent longs as long.js.
somewhat related #48
interesting. I will investigate how to support properly long with JS big int.
Let's keep that PR open.
Issue
When trying to compile a Typescript project that use
node-q
module, I get these error:fix
Remove references to Long that does not exist in TypeScript; usenumber instead