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

@awaitbox/document-ready

v2.0.1

Published

@awaitbox/document-ready ========================

Downloads

44

Readme

@awaitbox/document-ready

Await for the document to be ready.

npm i @awaitbox/document-ready --save

The documentReady async function returns a promise that will resolve when the DOMContentLoaded event fires in the future (i.e. when the document becomes "ready", a term that jQuery made popular), or resolves immediately if DOMContentLoaded already happened. Sub-resources (img tags, scripts, audio tags, etc) might not be done loading yet, and in this case you'll want to use window-loaded.

Learn more about the DOMContentLoaded event on MDN.

You can use it in async functions:

import documentReady from '@awaitbox/document-ready'

async function main() {
  await documentReady()
  console.log( 'Ready to begin awesome!' )
}

main()

You can of course use it as a Promise:

import documentReady from '@awaitbox/document-ready'

documentReady()
  .then( data => console.log( 'begin awesome!' ) )

Chain values will pass through if you use it in a Promise chain:

import documentReady from '@awaitbox/document-ready'

fetch( ... )
  .then( ... )
  .then( documentReady ) // passes data through
  .then( data => console.log( 'use data for the awesome!', data ) )

Note

This is written in ES2016 JavaScript. To use this in pre-ES2016 environments, you'll need to run this through a transpiler like Babel (and I recommend using the fast-async plugin to get the best results). See some tips here on wiring it up with Webpack: http://2ality.com/2017/06/pkg-esnext.html.