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

hobby-rpc.server

v0.1.2

Published

To create Hobby-RPC servers with Node.js

Downloads

64

Readme

Introduction

It is to create Hobby-RPC servers with Node.js. To install: npm i hobby-rpc.server.

Usage

Either require or import:

{ Server } = require 'hobby-rpc.server'
import { Server } from 'hobby-rpc.server'

Server is a function which returns an http.Server. It takes an object which must have the functions property.

Here is a simple server providing SomeNullaryFunction and SomeUnaryFunction:

server = Server
  functions:
    SomeNullaryFunction: ->
      'A string returned from SomeNullaryFunction.'
    SomeUnaryFunction: (input) ->
      "A string returned from SomeUnaryFunction with #{input}."

To start a server, you can use server.listen():

server.listen 8080
# or
server.listen '/path/to/unix.socket'

Functions

functions can return any objects serializable with JSON.stringify. If a function returns a rejected Promise or throws an error, the server responds with 400 Bad Request.

CORS headers

By default, it will return permissive CORS headers(Access-Control-Allow-Origin: *) for requests from any origin. For private APIs, you might want to restrict that:

server = Server
  CORS:
    Origins: ['https://some.domain', 'https://another.domain']
  functions:
    SomeNullaryFunction: ->
      'A string returned from SomeNullaryFunction.'
    SomeUnaryFunction: (input) ->
      "A string returned from SomeUnaryFunction with #{input}."

You can also override the default values as follows:

server = Server
  CORS:
    Methods: 'POST, OPTIONS'
    Headers: 'Authorization, Content-Type'
    MaxAge: '86400'
  functions:
    SomeNullaryFunction: ->
      'A string returned from SomeNullaryFunction.'
    SomeUnaryFunction: (input) ->
      "A string returned from SomeUnaryFunction with #{input}."

Authorization

By default, any client is allowed to call the functions. For public APIs, you will probably want to restrict that.

To do so, pass FindUser as follows:

server = Server
  FindUser: (token) ->
    if token is 'TheOnlyValidToken'
      name: 'A'
  functions:
    SomeNullaryFunction: ->
      "Hello, #{@user.name}."

FindUser should be a function that takes one argument, a String token. token is what clients are supposed to pass in the Authorization header.

If FindUser returns one of these:

  • a falsy value;
  • a rejected Promise;
  • a Promise resolved to a falsy value;

or throws an error, the server responds with 403 Forbidden.

If FindUser returns something else, the server will assume it is something that represents the current user. If it is a Promise, the value resolved from this Promise will be available inside of the functions as @user. If it is not a Promise, it itself will be available as @user.