[@types/node] NodeJS.Timer compatibility type no longer works #69943
Unanswered
connorjclark
asked this question in
Issues with a @types package
Replies: 1 comment
-
|
Thanks for the discussion about "node", some useful links for everyone: Pinging the DT module owners: @microsoft, @jkomyno, @alvis, @r3nya, @btoueg, @smac89, @Touffy, @DeividasBakanas, @eyqs, @Hannes-Magnusson-CK, @hoo29, @kjin, @ajafff, @islishude, @mwiktorczyk, @mohsen1, @galkin, @parambirs, @eps1lon, @ThomasdenH, @WilcoBakker, @wwwy3y3, @samuela, @kuehlein, @bhongy, @chyzwar, @trivikr, @yoursunny, @qwelias, @ExE-Boss, @peterblazejewicz, @addaleax, @victorperin, @ZYSzys, @nodejs, @LinusU, @wafuwafu13, @mcollina, @Semigradsky. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
For code like this:
Note the usage of
NodeJS.Timerrather thanNodeJS.Timeout, which is defined here:DefinitelyTyped/types/node/timers.d.ts
Lines 32 to 39 in 641755d
I receive errors like this:
[Symbol.dispose]was added recently, but not to the older type which remains for compatibility, so this introduced an error when I upgraded typescript recently which was a little difficult to diagnose.suggestions:
@deprecatedtag to the old type saying you should useNodeJS.Timeoutinsteaddisposeto the old type tooBeta Was this translation helpful? Give feedback.
All reactions