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

@glandjs/core

v2.0.0

Published

Glands is a web framework for Node.js (@core)

Readme

@glandjs/core

The transport-agnostic heart of Gland: module registration, dependency injection, metadata discovery, and the event bus that protocol adapters attach to.

npm install @glandjs/core @glandjs/common

Quick start

import { Module } from '@glandjs/common';
import { GlandFactory } from '@glandjs/core';
import { ExpressBroker } from '@glandjs/express';

@Module({ imports: [ProductModule] })
export class AppModule {}

const { app, shutdown } = await GlandFactory.create(AppModule);

const express = app.connectTo(ExpressBroker);
express.listen(3000);

process.on('SIGTERM', () => void shutdown('SIGTERM'));

create() resolves only after every lifecycle phase completes, so calling listen() on the next line cannot race route registration.

What this package provides

| Area | Export | | --------- | --------------------------------------------------------------- | | Bootstrap | GlandFactory, ApplicationInitial | | The bus | GlandBroker, TGlandBroker | | DI | Container, ModuleRef, ModulesContainer, InstanceWrapper | | Discovery | Explorer, DiscoveryService, MetadataScanner | | Binding | ApplicationBinder, ApplicationLifecycle | | Lifecycle | LifecycleScanner, ProcessHooks, the hook interfaces | | Request | Context, UnknownEventError | | Extension | BrokerAdapter |

Design notes

create() is awaited. It used to be called without await, so an application could begin listening before its routes were bound.

DI fails loudly. A cycle raises CircularDependencyError naming the chain. An erased parameter type raises UnresolvableDependencyError explaining the fix. Neither case produces a silently undefined dependency.

Channel resolution is a single property read. The binder freezes one publicName -> brokerEvent registry at startup and shares it by reference, so a request never rebuilds a lookup table.

Handlers keep their this. A handler is extracted as a bare prototype function; the binder restores the instance at dispatch.

Unhandled rejections do not exit the process. They are logged. Signals shut the application down; a stray promise is a bug to fix, not a reason to drop traffic. See ProcessHookOptions.

Documentation

License

MIT