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

@brainhubeu/hadron-core

v1.0.0

Published

Hadron core module

Downloads

31

Readme

Installation

  • Install Node.js. We recommend using the latest version, installation details on nodejs.org

  • Install following modules from npm:

npm install @brainhubeu/hadron-core @brainhubeu/hadron-express express --save

Hello world app

Let's start with traditional Hello World app. It will give you a quick grasp of the framework.

const hadron = require('@brainhubeu/hadron-core').default;
const express = require('express');

const port = 8080;
const expressApp = express();

const config = {
  routes: {
    helloWorldRoute: {
      path: '/',
      callback: () => 'Hello world!',
      methods: ['get'],
    },
  },
};

hadron(expressApp, [require('@brainhubeu/hadron-express')], config).then(() => {
  expressApp.listen(port, () =>
    console.log(`Listening on http://localhost:${port}`),
  );
});

In the sections below, we will describe step by step what just happened.

Bootstrapping an app

The main hadron-core function is responsible for bootstrapping the app. It registers packages based on passed config and server instance:

const hadron = require('hadron-core').default;

hadron(serverInstance, [...packages], config);

The purpose of the main function is to initialize DI container and register package dependencies according to correspondent sections in config object (described in details in next chapters).

Main function returns a promise that resolves to created DI container instance. In the promise .then() method, besides performing operations on the container instance, we can actually start our server, by calling Express listen method:

hadron(serverInstance, ...rest).then((container) => {
  // do some things on container...

  serverInstance.listen(PORT, callback);
});

Now, let's move to DI container itself.

Dependency Injection

The whole framework is built around DI Container concept. Its purpose is to automatically supply proper arguments for routes callbacks and other framework's building blocks.

DI container instance is created and used internally by bootstrapping function, it is also returned (as a promise) from bootstrapping function, as mentioned in the previous section.

Container methods

Registering items

container.register(key, item, lifetime);
  • key - item name on which it will be registered inside the container
  • item - any value (primitive, data structure, function, class, etc.)
  • lifetime - the type of item's life-span

Lifetime options:

  • 'value' - container returns registered item as is [default]
  • 'singleton' - returns always the same instance of registered class / constructor function
  • 'transient' - returns always a new instance of registered class / constructor function

Retrieving items

container.take(key);
  • key - item name (same as provided during registration)

The method returns item or item instance according to item type and lifetime option.

Example usage in bootstrapping function

const { default: hadron, Lifetime } = require('hadron-core');

hadron(...args).then((container) => {
  container.register('foo', 123);
  container.register('bar', class Bar {}, Lifetime.Singleton);
  container.register('baz', class Baz {}, Lifetime.Transient);

  // other stuff...
});

Accessing container items from routes' callbacks

To access container items from callbacks, you can just set arguments' names to match container keys, and required dependency will be provided.

See an example here