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

lazy-promise-loader

v1.0.0

Published

promise-loader with lazy promises

Downloads

4

Readme

lazy-promise-loader

Like promise-loader, but with lazy promises (no invocation required).

Promise is expected to be available in the global scope.

Usage

Documentation: Using loaders

const _file = require('lazy-promise!./file.js')

// file will not be loaded until `.then()` is invoked
setTimeout(() => _file.then((file) => ...), 1000)

// or in ES2017
async function someHandler() {
  const file = await _file
}

Optionally specify a name for your chunk...

const load = require("lazy-promise?editor!./editor.js")

Why bother? For APIs that expect promises before the chunk is to be loaded. That's why.

For example, say you have an API that accepts both functions, and promises that return functions, and these functions should not be invoked until some later time.

With the regular 'ol promise-loader, there is no way to programatically tell which is which.