npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

fast-future

v1.0.2

Published

A really fast way to run a callback in the future

Downloads

39,428

Readme

fast-futurebuild status

A really fast way to run a callback in the future

NPM

NPM

Installation

npm install fast-future

What? How does is work?

Since node.js v0.10.x the semantics of process.nextTick changed (see docs). To get the old behaviour one can use setImmediate instead.

The good part about process.nextTick is that it's really really fast. The bad part is that event loop can be starved and if run for to long time it'll eventually die with a RangeError: Maximum call stack size exceeded.

What's good about setImmediate is that it won't starve the event loop. However, it's a bit slower than process.nextTick.

fast-future uses the best from the both worlds - the callback will most of the times be called in a process.nextTick, but once in a while it'll get run in a setImmediate - so you'll get crazy performance, and the event loop won't get starved or crash or something sad like that.

For me running the benchmarks show the following result

# setImmediate
setImmediate: 2317ms
# fastFuture
fastFuture: 96ms

For node v0.8.x it'll fallback to using process.nextTick

Example

var fastFuture = require('./fast-future')()

fastFuture(function () {
  console.log('this is being run in the future')
})

Kudos

Thanks @mafintosh for suggesting this!

Licence

Copyright (c) 2014 David Björklund

This software is released under the MIT license:

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.