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

@agentback/core

v0.13.0

Published

Core framework: Application, Component, Server, LifeCycle (ported from @loopback/core)

Readme

@agentback/core

Application, Component, Server, and lifecycle management — the framework layer above the DI container.

ESM port of @loopback/core. Application extends Context with typed registries for servers, components, controllers, and services. Components bundle bindings together so features can be plugged in with a single call. LifeCycleObserver coordinates init → start → stop across all registered pieces.

Re-exports everything from @agentback/context (and transitively from @agentback/metadata), so most packages only import from @agentback/core.

What it provides

  • Application — the root Context subclass; hosts start() / stop() / init(), signal handling, and graceful shutdown.
  • Component / mountComponent — plug in a bundle of bindings, controllers, servers, and lifecycle observers.
  • Server — minimal interface for objects that participate in the lifecycle (start / stop).
  • LifeCycleObserver / LifeCycleObserverRegistry / asLifeCycleObserver — ordered init/start/stop orchestration across all registered observers.
  • CoreBindings / CoreTags — well-known binding keys and tag names (application.instance, servers, components, controllers, services, lifeCycleObserver, …).
  • ExtensionPoint / extensionPoint / extensions — extension-point/extension pattern for pluggable feature sets.
  • createServiceBinding / ServiceOptions — register an arbitrary class as a named service in the container.
  • isMain(import.meta) — ESM equivalent of require.main === module.
  • mixinTarget — utility for building mixin classes against Application.

Usage

import {Application, Component, Server, CoreBindings} from '@agentback/core';

class PingServer implements Server {
  async start() {
    console.log('listening…');
  }
  async stop() {
    console.log('closed.');
  }
}

class PingComponent implements Component {
  servers = {ping: PingServer};
}

const app = new Application({name: 'my-app'});
app.component(PingComponent);

await app.start();
// -> 'listening…'
await app.stop();
// -> 'closed.'

Inject the application itself anywhere inside the container:

import {inject} from '@agentback/core';
import {CoreBindings} from '@agentback/core';

class MyService {
  constructor(
    @inject(CoreBindings.APPLICATION_INSTANCE) private app: Application,
  ) {}
}

Layering

Depends on: @agentback/context (which re-exports @agentback/metadata).
@agentback/core is the framework base that rest, mcp, config, authentication, and every example depend on.