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

@jamen/hyperserver

v0.0.0

Published

Route some actions through your server, and elsewhere offline.

Downloads

3

Readme

@jamen/hyperserver

Tiny WebSocket server that hooks into Hyperapp

Provdies a WebSocket server that hooks into Hyperapp actions.

It adds "remote actions", which are simply actions that get their data transformed through your server. The different can be visualized as:

Normal action:

    Action +---> State +---> View


Remote action:

    Action +- - - - - -Offline?- - - - - - -> State +---> View
             \                            /
    (Servers) +---Request-----Response---+

Install

npm i -D @jamen/hyperserver

Usage

server(props)

Creates a WebSocket server with

  • messages handling each incomming action.
  • host being address of the server. (Defaults to localhost)
  • port being port of the server. (Defaults to 3001)
  • error(err) being called

Each message looks like name(request, response). They receive and send messages formated as [name, data], which correlates to actions client-side. For example:

server({
  messages: {
    token (req, res) {
      // Receive "token" action from client
      console.log(req.data)

      // Respond with "token" action on client
      res.send('token', {
        token: randomBytes(8).toString('hex')
      })
    }
  }
})

See below for handling responses.

remote(app, options)

An extension to Hyperapp which adds props.remote for specifying remote actions. It connects to the Hyperserver with

  • host being the address of the server. (Defaults to localhost)
  • port being the port of the server. (Defaults to 3001)

Remote actions are like regular actions except they ask a server first.

Action +- - - - - -Offline?- - - - - - -> State +---> View
         \                            /
(Servers) +---Request-----Response---+

An example of using the extension:

app = remote(app)

app({
  state: {
    count: 0
  },
  remote: {
    add: (state, actions) => data {
      return { count: data.count + 1 }
    }
  },
  view: (state, actions) => (
    h('button', { onclick: actions.add }, state.count)
  )
})

Everything defined in remote is available as actions everywhere else. Note remote actions take precedence of normal actions.