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

socketio-rest

v1.0.0

Published

Websockets are way faster than http. This package seeks to provide a replacement for http when creating RESTful APIs.

Downloads

7

Readme

Motivation

Websockets are way faster than http. This package seeks to provide a replacement for http when creating RESTful APIs.

To do

  • Limit calls to WATCH handler so that it's only called when the matches of the query is changed. Now it is triggered for all changes within a resource.
  • Move CHANGE-events away from strategy

Usage

Client

import {Frontend} from 'socketio-rest'
import socketio from 'socket.io-client'

const io = socketio('http://localhost')
const realtime = new Frontend(io)

// Meta data for all messages

realtime.options.token = 'some jwt token'

// Create

async function createUser(options) {
  return realtime.create('users', options)
}

// Read

async function getUser(id) {
  return realtime.getOne('users', { id })
}

async function getUserByEmail(email) {
  return realtime.getOne('users', { email })
}

async function getAllUsers() {
  return realtime.get('users')
}

async function getAdminUsers() {
  return realtime.get('users', { role: 'admin' })
}

// Watch/unwatch

async function watchAdminUsers() {
  const watchId = await realtime.watch('users')

  return function unwatch() {
    return realtime.unwatch(watchId)
  }
}

async function watchAdminUsers() {
  const watchId = realtime.watch('users', { role: 'admin' })

  return function unwatch() {
    return realtime.unwatch(watchId)
  }
}

// Update

async function updateRole(userId, newRole) {
  return realtime.update('users', { role: newRole })
}

// Delete

async function deleteUser(id) {
  return realtime.destroy('users', { id })
}

Server

import {Backend} from 'socketio-rest'
import EventEmitter from 'events'
import socketio from 'socket.io'
import http from 'http'

const server = http.createServer()
const io = socketio(server)
const events = new EventEmitter()
const resources = ['users']

const databaseAdapter = {
  async getOne(resource, query, metaData) {
    // Return one instance of the resource matching the query
    // ‹Your implementation›
  },
  async get(resource, query, metaData) {
    // Return an array of instances matching the query
    // ‹Your implementation›
  },
  async update(resource, updates, metaData) {
    // Update an instance of the query using updates = { id, ...updates }
    // ‹Your implementation›

    // Then notify socketio-rest that a change has occurred
    events.emit('CHANGE ' + resource)
  },
  async create(resource, data, metaData) {
    // Create an instance of the resource
    // ‹Your implementation›

    // Then notify socketio-rest that a change has occurred
    events.emit('CHANGE ' + resource)
  },
  async destroy(resource, query, metaData) {
    // Delete an instance of the resource
    // ‹Your implementation›

    // Then notify socketio-rest that a change has occurred
    events.emit('CHANGE ' + resource)
  }
}

// Initialize

const realtime = new Backend(io, resources)

// Specify a strategy

const strategy = {
  db,
  events,
}

realtime.useStrategy(strategy)

server.listen(1234, () => {
  console.log('Server listening on port 1234')
})

Testing

yarn test
npm test