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

@tiny-broke/client

v0.3.2

Published

Javascript client for [tiny-broke](https://github.com/fabienjuif/tiny-broke).

Downloads

18

Readme

@tiny-broke/client

Javascript client for tiny-broke.

Service

import connect from '@tiny-broke/client'

// connect to tiny-broke
const broke = connect(
  'invoices', // service name
  'tcp://localhost:3000', // tiny-broke uri
  true, // is it a worker? yes
)

// your service
const get = async (action) => {
  // this is here you are doing your stuff, like requesting your DB

  return {
    id: action.payload,
    price: 2342,
  }
}

// you register your `get` service behind `INVOICES>GET` event
// when tiny broke recieve the `INVOICES>GET` event it will call the logger callback first
broke.register(
  'INVOICES>GET', // register to this event type
  get, // calls this service to process the data and return a response
  (action) => console.log('getting invoice by id', JSON.stringify(action)), // log this when the event arrives (can be omitted)
)

Client

import connect from '@tiny-broke/client'

// connect to tiny-broke
const broke = connect(
  'graphql-api', // client name
  'tcp://localhost:3000', // tiny-broke uri
  false, // is it a worker? no this is a client
)

// event factory helper
const getInvoice: id => ({
  type: 'INVOICES>GET', // event type, must match a register from a service
  returnsType: `INVOICES>GET>${id}`, // this type is used to tells tiny-broke that we are waiting this response to complete
  payload: id, // whatever you want in payload, here the invoice id
})

const run = async (id) => {
  // ask a worker to process the `INVOICES>GET` event
  // and wait for the result
  const invoice = await broke.wait(getInvoice(id))

  // this is here you put your further processing
  console.log(invoice)
}

run(10)