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

JQDeferred

v2.1.0

Published

jQuery deferreds source and unit tests ported verbatim to nodejs using minimal, automated, code transformation

Downloads

152

Readme

jQuery Deferreds for nodejs

jQuery Deferreds source and unit tests ported verbatim to nodejs using minimal, automated, code transformation.

Rationale

This is the exact same code, running the exact same unit tests. Why use a bad copy when you can use the original?

Installation

  • use npm: npm install JQDeferred
  • or put JQDeferred as a dependency in package.json.

Using

var Deferred = require( "JQDeferred" );

Correspondences

| jQuery | JQDeferred | | -------------:|:--------------------:| | $.Deferred | Deferred | | $._Deferred | Deferred._Deferred | | $.when | Deferred.when | | $.Callbacks | Deferred.Callbacks |

_Deferred only available prior to 1.7.0

Callbacks only available as of 1.7.0.

Documentation

Just head to the jQuery API site:

Versioning

There is an exact correspondence between the version of the package and the version of jQuery from which it has been extracted. So, if you want to use Deferreds as they were in jQuery 1.5.2, just use npm install [email protected].

Of course, this is not really semantic versioning but it makes a lot more sense than maintaining a separate version.