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 🙏

© 2026 – Pkg Stats / Ryan Hefner

partyline-ts-server

v0.1.0

Published

NodeJS package to interface with partyline

Downloads

3

Readme

partyline-ts-server

NodeJS package to interface with partyline

This package is an interface for the PartyLine API Specification

Code Source on gitlab.com

API

PartyLineRouter

This is an express router, which has to be used like this :

var app = express()
PartyLineRouter(app)

app.listen(8080, () => {
  console.log("PartyLine server running on port 8080")
})

This is a typescript class that can be supercharged. The following methods are interesting, and this is their current implementation :

async getUser(id: string): Promise<PLUser> {
  return PLExamples.user
}

async getGroup(id: string): Promise<PLGroup> {
  return PLExamples.group
}

async getPost(id: string): Promise<PLPost> {
  return PLExamples.post
}

async deletePost(id: string): Promise<Status> {
  console.info(`DELETE ${id}. No action done.`);
  return Status.NotImplemented;
}


async newPost(post: PLPost): Promise<Status> {
  console.info("NEW post: ", post)
  return Status.NotImplemented
}


async editPost(post: PLPost): Promise<Status> {
  console.info("EDIT post: ", post)
  return Status.NotImplemented
}


async commentPost(post: PLPost, id: string): Promise<Status> {
  console.info(`COMMENT on post ${id}: `, post)
  return Status.NotImplemented
}


async commentEvent(post: PLPost, id: string): Promise<Status> {
  console.info(`COMMENT on Event ${id}: `, post)
  return Status.NotImplemented
}


async newEvent(event: PLEvent) {
  console.info(`NEW EVENT:`, event)
  return Status.NotImplemented
}


async getEvent(id: string): Promise<PLEvent> {
  return PLExamples.event
}

async deleteEvent(id: string): Promise<Status> {
  console.info("DELETE event: ", id)
  return Status.NotImplemented
}

async getEvents(ts: string): Promise<PLEvent[]> {
  return [PLExamples.event, PLExamples.event, PLExamples.event]
}

async editEvent(event: PLEvent): Promise<Status> {
  console.log("EDIT event :", event)
  return Status.NotImplemented
}

PLUser, PLGroup, PLAuthor, PLEvent, PLPost

Those interfaces are defined in types.ts in accordance with the the specification

PartyLineServer

A function that instances an express server, configures it with PartyLineRouter, and returns it.

Usage :

var app = PartyLineServer()