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

do-listen

v1.0.3

Published

Listen to a server and call a callback on error or success

Downloads

1

Readme

do-listen

Build Status Coverage Status

Properly call callback on a node server on the listening or error event.

Why?

I continue to see the following:

const http = require('http')
const server = http.createServer()
server.listen((err) => { // `err` won't be passed here
  if (err) throw err
})

The problem with that is that the cb passed to the listen function is only added as an event listener for the listening event.

i.e. no err will ever be passed back.

In order to properly wait for either the listening event or error event without leaking listeners:

function doListen(server, cb) {
  var called = false
  const done = (err) => {
    if (called) return
    server.removeListener('error', done)
    server.removeListener('listening', done)
    called = true
    cb(err)
  }

  server.on('error', done)
  server.on('listening', done)
}

which is literally what the package is :]

Install

$ npm install do-listen

Examples

'use strict'

const net = require('net')
const doListen = require('do-listen')

const server = net.createServer()
server.listen(0)
doListen(server, (err) => {
  if (err) throw err
  console.log('listening on', server.address().port)
})

This also works with http

'use strict'

const http = require('http')
const doListen = require('do-listen')

const server = http.createServer()
server.listen(8080)
doListen(server, (err) => {
  if (err) throw err
  console.log('listening on', server.address().port)
})

Want to use with promises or async/await?

'use strict'

const http = require('http')
const {promisify} = require('util')
const doListen = require('do-listen')

const server = http.createServer()
server.listen(8080)
async function main() {
  await doListen(server)
}

// or

'use strict'

const http = require('http')
const {promisify} = require('util')
const doListen = require('do-listen')

const server = http.createServer()
server.listen(8080)
doListen(server).then(() => {
  console.log('listening on', server.address().port)
}).catch((err) => {
  throw err
})

Test

$ npm test

Author

Evan Lucas

License

MIT (See LICENSE for more info)