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

divisions

v0.1.4

Published

Minimalist modular backend development

Downloads

41

Readme

Divisions 🌿

Minimalist modular backend development

Modular Node.js backend development, management, and orchestration of backend applications.

It promotes a clean separation of concerns by structuring applications into distinct functional units, called "divisions".

Features

  • 🧩 Modular Design: Clean architectural separation into distinct divisions.
  • 🔗 Dependency Management: Ensures correct initialization order of divisions.
  • Environment Variables Validation: JSON Schema validation for environment variables.
  • 🖥 CLI Integration: Defines and executes division-specific commands.
  • 🍃 Dynamic Lifecycle Management: Custom setup and teardown routines for resource management.

Motivation

In complex applications, managing configurations, dependencies, and initialization order can become challenging.

Divisions was created to address these challenges by offering a structured way to organize application logic into manageable, isolated modules.

This approach not only improves code maintainability but also enhances the development workflow by providing clear interfaces for each part of the application.

Inspired by the modular philosophy, Divisions aims to bring simplicity, clarity, and efficiency to backend application development.

Getting Started

Prerequisites

Node.js version 20.11.0 or higher is required.

Installation

Install divisions via npm/yarn/pnpm:

npm install divisions

Setup

Our goal is to create a division called http to create our http server.

  1. Create the divisions directory. It will contains all our divisions directories.
  2. Create your first division directory divisions/http.
  3. Create divisions/http/index.js with the following content:
// divisions/http/index.js
import http from "node:http";

export const meta = {
  // Define environment variables schema for validation
  envSchema: {
    type: "object",
    properties: {
      PORT: { type: "integer" },
    },
    required: ["PORT"],
  },
};

// Define division setup
export function setup({ config }) {
  const httpServer = http.createServer((_request, response) => {
    response.writeHead(200, { "Content-Type": "text/plain" });
    response.end("Hello from http division 👋");
  });

  return {
    // On start `http` division
    start() {
      httpServer.listen(config.PORT, () => {
        console.info(`HTTP Server running at http://localhost:${config.PORT}`);
      });

      return {
        // Close `http` division in a clean way
        cleanup() {
          httpServer.close();
          console.info("HTTP Server has been closed");
        },
      };
    },
  };
}
  1. Create a .env file at the root of your project containing all environment variables used by our divisions.
PORT=3000
  1. Create index.js to start divisions. This operation will import your divisions and execute them.
import { startDivisions } from "divisions";

startDivisions().catch(console.error);

By the end, your project structure should look like this:

.
├── divisions
│   └── http
│       └── index.js
├── index.js
├── package.json
  1. Launch it !
❯ node index.js
HTTP Server running at http://localhost:3000

❯ curl http://localhost:3000
Hello from http division 👋

Contributing

Contributions are welcome! Submit issues, feature requests, or pull requests 🤝.

License

Made with 💚

Published under the MIT license.

Acknowledgements

Inspired by the modular design philosophy and contributions to the open-source Node.js ecosystem by developers worldwide 🙌