/ piacw.com / dev / final / node_modules / timers-browserify /

[ICO]NameLast modifiedSizeDescription
[PARENTDIR]Parent Directory  -  
[TXT]CHANGELOG.md2 years ago3.0K0fb859dc fixed mobile overflwo options [كارل مبارك]
[TXT]LICENSE.md2 years ago2.4K0fb859dc fixed mobile overflwo options [كارل مبارك]
[TXT]README.md2 years ago1.2K0fb859dc fixed mobile overflwo options [كارل مبارك]
[   ]main.js2 years ago2.0K0fb859dc fixed mobile overflwo options [كارل مبارك]
[   ]package.json2 years ago2.7K0fb859dc fixed mobile overflwo options [كارل مبارك]
README.md

Overview

Adds support for the timers module to browserify.

Wait, isn't it already supported in the browser?

The public methods of the timers module are:

and indeed, browsers support these already.

So, why does this exist?

The timers module also includes some private methods used in other built-in Node.js modules:

These are used to efficiently support a large quantity of timers with the same timeouts by creating only a few timers under the covers.

Node.js also offers the immediate APIs, which aren't yet available cross-browser, so we polyfill those:

I need lots of timers and want to use linked list timers as Node.js does.

Linked lists are efficient when you have thousands (millions?) of timers with the same delay. Take a look at timers-browserify-full in this case.

License

MIT

Apache/2.4.38 (Debian) Server at www.karls.computer Port 80