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

@lokiverse/emitter

v0.1.0

Published

TypeScript-first event emitter with proper namespacing, type safety, and wildcard support

Downloads

60

Readme

npm version License: MIT TypeScript codecov

The Good Parts

TypeScript

import { createEmitter } from '@lokiverse/emitter'

type Events = {
  'meeting:endless': { minutesWasted: number }
  'meeting:scheduled': { conflictsWithLunch: boolean }
  'meeting:cancelled': { excuseQuality: number }
}

const emitter = createEmitter<Events>()

// Your IDE actually knows what's going on
emitter.meeting.$on('endless', ({ minutesWasted }) => {
  if (minutesWasted < 60) {
    console.log('That was just a warm-up')
  }
  if (minutesWasted > 120) {
    console.log('Time to update the resume')
  }
})

Features

  • 🎯 Actually Type-Safe: Because any is just admitting defeat
  • 🌳 Proper Namespacing: Not the "string prefix" kind of fake namespacing
  • 🃏 Wildcard Listeners: Like RegEx, but without the therapy sessions
  • 🚀 Zero Dependencies: No node_modules black hole
  • 🤏 Tiny Bundle: Smaller than your last code review comments

Installation

pnpm add @lokiverse/emitter

Usage

Basic Usage (That Actually Works)

// Define events (with real types, not "documentation")
type GitEvents = {
  'commit:push': { message: string; boringLevels: number }
  'commit:revert': { excuse: string }
}

const git = createEmitter<GitEvents>()

// Your IDE is now your friend
git.commit.$on('push', ({ message, boringLevels }) => {
  if (message.includes('fix typo')) {
    console.log('Sure it was "just" a typo')
  }
})

One-Time Events

// For those "it worked on my machine" moments
git.commit.$once('revert', ({ excuse }) => {
  console.log(`Saving ${excuse} for future use`)
})

Wildcard Magic

// Catch all the things related to commits
git.commit.$on('*', (event, data) => {
  console.log(`Git did something: ${event}`, data)
  // Perfect for those "what just happened?" moments
})

// Use wildcards with namespaces as flat as earth
git.$on('commit:*', (event, data) => {
  console.log(`Revert or commit? That is the question: ${event}`, data)
})

Namespace Like You Mean It

// Split your concerns (unlike your PRs)
const commitEvents = git.$ns('commit')
commitEvents.$on('push', handlePush) // Clean and tidy

Real World Examples (Because We All Copy-Paste)

Error Handling

type ErrorEvents = {
  'error:404': { url: string; lastSeenAlive: Date }
  'error:500': { stack: string; blame: string }
}

const emitter = createEmitter<ErrorEvents>()

emitter.error.$on('500', ({ stack, blame }) => {
  console.log(`Time to blame ${blame || 'the intern'}`)
})

Feature Flags

type FeatureEvents = {
  'feature:enabled': { name: string; whoToBlame: string }
  'feature:disabled': { name: string; excuses: string[] }
}

const emitter = createEmitter<FeatureEvents>()

emitter.feature.$on('enabled', ({ name, whoToBlame }) => {
  console.log(`${name} is now enabled. If it breaks, talk to ${whoToBlame}`)
})

Contributing

Found a bug? Open an issue. Have a fix? PR welcome.

Just remember: With great type safety comes great responsibility.

License

MIT © Lokiverse