Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / Krb686/nanotimer issues and pull requests

#27 - Added TypeScript Support

Pull Request - State: open - Opened by roblav96 over 6 years ago

#26 - First Call on setInterval

Issue - State: open - Opened by akashbudhia about 7 years ago

#25 - Check if timeOut is defined

Issue - State: closed - Opened by akashbudhia over 7 years ago - 1 comment

#24 - "process.hrtime is not a function"

Issue - State: closed - Opened by DaleSalcedo over 7 years ago

#23 - Add license (ISC)

Pull Request - State: closed - Opened by hassy almost 9 years ago - 2 comments

#22 - test: add test for testing the async callback format

Pull Request - State: closed - Opened by joscha almost 9 years ago - 1 comment

#21 - fix: add mocha & should as development dependencies & set timeout higher

Pull Request - State: closed - Opened by joscha almost 9 years ago

#20 - unit passed to .time() function ignored.

Issue - State: closed - Opened by joscha almost 9 years ago - 4 comments

#19 - Fix package.json to use correct filename

Pull Request - State: closed - Opened by lmommaerts about 9 years ago

#18 - 0.3.11 on Ubuntu isn't loading

Issue - State: closed - Opened by rob-gordon about 9 years ago - 4 comments

#17 - Fix #16 where this.timeOutT1 is sometimes null

Pull Request - State: closed - Opened by lmommaerts about 9 years ago - 1 comment

#16 - process.hrtime() only accepts an Array tuple.

Issue - State: closed - Opened by apladas about 9 years ago - 6 comments

#15 - Fix global leak.

Pull Request - State: closed - Opened by zackiles about 9 years ago

#14 - setIntervall - memory permanently increasing

Issue - State: closed - Opened by fatelgit over 9 years ago - 14 comments

#13 - Bug in first example

Issue - State: closed - Opened by tlanier9 over 9 years ago - 1 comment

#11 - Not suitable as a drop in replacement of setTimeout

Issue - State: closed - Opened by gblazex over 9 years ago - 10 comments

#10 - How can I destroy the timer after it's been called?

Issue - State: closed - Opened by felixchan over 9 years ago - 1 comment

#9 - timer.setInterval() takes interval as args

Issue - State: closed - Opened by Tilogorn over 9 years ago - 2 comments

#8 - io.js compat

Issue - State: closed - Opened by cyrusdavid almost 10 years ago - 3 comments

#7 - clearInterval causes RangeError: Maximum call stack size exceeded

Issue - State: closed - Opened by rsmck almost 10 years ago - 2 comments

#6 - First few intervals are way off

Issue - State: closed - Opened by ImmanuelSamuel almost 10 years ago - 4 comments

#5 - calling setTimeout right after clearTimeout gets ignored?

Issue - State: closed - Opened by kanecko almost 10 years ago - 8 comments

#4 - clearTimeout

Issue - State: closed - Opened by omarojo about 10 years ago - 3 comments

#3 - setInterval High CPU usage

Issue - State: closed - Opened by spood over 10 years ago - 8 comments

#2 - broken API compatibility of setInterval for 0.2.x

Issue - State: closed - Opened by alxlo about 11 years ago - 2 comments

#1 - Module not found on case sensitive systems

Pull Request - State: closed - Opened by davebond almost 12 years ago