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

hexa-onion

v1.1.0

Published

Basic helper module for dependency injection in an hexagonal / onion architecture

Readme

hexa-onion

Basic helper module for dependency injection in an hexagonal / onion architecture.

Overview

This light 2-classes modules helps:

  • building an application layer by layer, wrapped one around the other
  • populating layers with services
  • accessing dependencies from a service:
    • either other services from the same layer
    • or "port" services from the immediate inner layer
    • or "plugin" services from the immediate outer layer

Installation

$ npm install hexa-onion

Usage

Build a 2 layers architecture with its services:

// ./index.js
const hexaOnion = require("hexa-onion");

// Domain layer
let dom = new hexaOnion.Layer();
dom.addService("answer", require("./dom/answer"));
dom.addPort("question", require("./dom/question"));

// Application layer
let app = new hexaOnion.Layer(dom);
app.addPlugin("db", require("./app/json-db"));
app.addPort("server", require("./app/express-server"));

Write service classe by extending the Service class, for services to access :

  • other services of the same layer using this.services :
// ./dom/question
const hexaOnion = require("hexa-onion");

class Question extends hexaOnion.Service {
    async ask() {
        let answer = await this.services.answer.getAnswer();
        return answer;
    }
}

module.exports = Question;
  • plugin services of the outer layer using this.plugins:
// ./dom/anwser
const hexaOnion = require("hexa-onion");

class Answer extends hexaOnion.Service {
    async getAnswer() {
        let answer = await this.plugins.db.readAnswer();
        return answer;
    }
}

module.exports = Answer;
  • and/or port services of the inner layer using this.ports:
// ./app/express-server
const hexaOnion = require("hexa-onion");
const express = require("express");

class ExpressServer extends hexaOnion.Service {
    listen() {
        let app = express();
        app.get("/question", async function(req, res) {
            res.send(await this.ports.question.ask());
        });
        app.listen(8080, function() {
            console.log("Server listening on port 8080...");
        });
    }
}

module.exports = ExpressServer;

And finally start the application by calling one of the external ports:

// back to ./index.js
inf.ports.server.listen();