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

@boostkit/core

v0.0.7

Published

Application bootstrap, service provider lifecycle, and framework-level runtime orchestration.

Readme

@boostkit/core

Application bootstrap, service provider lifecycle, and framework-level runtime orchestration.

Installation

pnpm add @boostkit/core

Usage

import { Application } from '@boostkit/core'
import { hono } from '@boostkit/server-hono'
import { RateLimit } from '@boostkit/middleware'

export default Application.configure({
  server:    hono(configs.server),
  config:    configs,
  providers,
})
  .withRouting({
    web:      () => import('../routes/web.js'),
    api:      () => import('../routes/api.js'),
    commands: () => import('../routes/console.js'),
  })
  .withMiddleware((m) => {
    m.use(RateLimit.perMinute(60))
  })
  .withExceptions((e) => {
    e.render(PaymentError, (err) =>
      new Response(JSON.stringify({ code: err.code }), {
        status: 402,
        headers: { 'Content-Type': 'application/json' },
      })
    )
    // ValidationError → 422 JSON is handled automatically — no need to register it
  })
  .create()

API Reference

  • ServiceProvider
  • Listener, EventDispatcher, dispatcher, dispatch(), events()
  • Application, AppConfig
  • ConfigureOptions, RoutingOptions
  • MiddlewareConfigurator, ExceptionConfigurator
  • AppBuilder, BoostKit
  • app(), resolve()
  • defineConfig()
  • Re-exports from @boostkit/artisan, @boostkit/support, and @boostkit/contracts types plus built-in DI and Events primitives

Configuration

  • AppConfig
    • name?, env?, debug?
    • providers?
    • config? (config object bound into the container)
  • ConfigureOptions
    • server, config?, providers?

Events

import { dispatch, dispatcher, events } from '@boostkit/core'

// Define an event
class UserCreated {
  constructor(public readonly id: number) {}
}

// Define a listener
class SendWelcomeEmail {
  async handle(event: UserCreated) {
    await mailer.send(event.id)
  }
}

// Register via provider in bootstrap/providers.ts
import { events } from '@boostkit/core'
export default [
  events({ UserCreated: [SendWelcomeEmail] }),
]

// Dispatch anywhere
await dispatch(new UserCreated(42))

EventDispatcher API

| Method | Description | |--------|-------------| | register(name, ...listeners) | Register listeners for an event name. Use '*' for wildcard (all events). | | dispatch(event) | Dispatch to matching listeners, then wildcard listeners. Awaited in order. | | count(name) | Number of listeners for an event name. | | hasListeners(name) | true if at least one listener is registered. | | list() | Record<string, number> snapshot of all registered events and counts. | | reset() | Clear all listeners (testing / hot-reload). |

Exception Handling

.withExceptions((e) => {
  // Custom error type → custom response
  e.render(PaymentError, (err) =>
    new Response(JSON.stringify({ code: err.code }), {
      status: 402,
      headers: { 'Content-Type': 'application/json' },
    })
  )

  // Re-throw to surface in dev error page / 500 in prod
  e.ignore(InternalDebugError)

  // ValidationError → 422 JSON is handled automatically
})

Notes

  • Application.create() is singleton-based and can recreate in development/local mode when config is passed.
  • BoostKit.boot() boots providers; BoostKit.handleRequest() lazily creates the HTTP handler.
  • ValidationError is always caught by the exception handler and returned as 422 JSON — no try/catch needed in routes.