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

hbi

v3.3.2

Published

Hosting Based Interfacing

Downloads

7

Readme

Hosting Based Interfacing

Example Client:


const hbi = require('hbi')

let port = 3321,
    host = '192.168.0.115'
let hbic = new hbi.HBIC({
    console: console,
    os: require('os'),
    told: rhn => console.log(`Ahah, now I know ${host}:${port} is hosted by ${rhn}`)
})
hbic.wire(require('net').connect(port, host, ()=>{
  hbic.send(String.raw `
    console.log("This is a HI from ${os.hostname()}.\nI know you can see you're on host " + os.hostname() + ", but I can't see that!")
    console.log(" umm... unless...")
    sendBack('told(' + JSON.stringify(os.hostname()) + ')')
  `)
}))

Example Server:


const hbi = require('hbi')

let port = 3321,
    host = '192.168.0.115'

// share a single hbi context for all connected clients
let hbiCtx = {
  // here too many artifacts are exposed, DO NOT do this in real HBI applications
  console: console,
  os: require('os')
}

let svr = require('net').createServer((socket) => {
  let hbic = new hbi.HBIC(hbiCtx)
  hbic.on(hbi.PACK_EVENT, (packet, payload) => {
    console.log('[hbi server got packet of type ', typeof(packet), ']:', packet, '\n[hbi flew code]:', payload)
  })
  hbic.on(hbi.WIRE_ERR_EVENT, (err) => {
    console.log('[hbic wire error in server]:', err.stack || err)
  })
  hbic.on(hbi.PEER_ERR_EVENT, (err) => {
    console.log('[hbi landing error in client side]:', err)
    console.log('[disconnecting hbi] ...')
    hbic.disconnect()
  })
  hbic.on(hbi.LANDING_ERR_EVENT, (err) => {
    console.log('[hbi landing error in server side]:', err.stack || err)
    console.log(' ** normally the situation should be analyzed and avoided **')
    console.log(' ** sending the err as peer err to client now **')
    hbic.sendPeerError(err)
  })
  hbic.wire(socket)
})
svr.on('listening', () => {
  console.log('[hbi server listening]:', host+':'+port)
})
svr.listen(port, host)