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

candy-box

v0.0.6

Published

Manage your modules classify, and provide Dependency Injection for them.

Downloads

8

Readme

Candy-Box

Manage your modules classify, and provide Dependency Injection for them.

Features

  • Auto load the modules in the directories you assign.

  • Provide DI for the registered modules.

  • Prevent the registered modules to be retrieved directly.

Get Started

  1. Install candy-box:

    $ npm i candy-box
  2. Write your configs in a candyboxrc.json:

    candyboxrc.json:

    {
      "injectSelf": true, // Inject itself to the modules of a provided context, default `true`.
      "camelCaseKey": true, // Change name of module and context to be "camelCase", default `true`.
      "capitalizeInitial": { // Capitalize the initial letter of a name, only active when `camelCaseKey` is true, default `true`.
        "module": true, // Active on module name, default `true`.
        "contextKey": true // Active on context name, default `true`.
      },
      "oneWayDependency": true, // One-way dependencies, default `true`.
      "context": {
        "./path/to/dir1": {
          "injectSelf": false, // Rewrite `config.injectSelf` locally.
          "camelCaseKey": true, // Rewrite `config.camelCaseKey` locally.
          "capitalizeInitial": true, // Rewrite `config.capitalizeInitial` locally.
          "name": "DAOs" // Rewrite the context name.
          // "dependencies": ["Dir2"], // Illegal dependencies.
        },
        "./path/to/dir2": {
          "dependencies": ["Dir1"],
          "skip": ["Module2"], // Skip loading the assigned modules.
          "childrenConfigs": {
            "User": {
              "dependencies": ["Dir1.Module1"],
              "mergeDependencies": false
            }
          }
        }
      }
    }
  3. Define your modules in the directories you assigned in configs, for example:

    dir1/module1.js:

    module.exports = ctx => {
        let Dir1;
        ctx.onInitialized(() => {
            Dir1 = ctx.Dir1; // Yes, you can get the modules under the "dir1".
        });
        return {
            fn () {
                // your bussiness code.
                return 'dir1/module1';
            }
        };
    };

    dir2/module1.js:

    // const Dir1Module1 = require('path/to/dir1/module1'); // Cannot get the correct module.
    
    module.exports = ctx => {
        let Dir1;
        ctx.onInitialized(() => {
            Dir1 = ctx.Dir1;
        });
        return {
            fn () {
                // your bussiness code.
                console.log(Dir1.Module1.fn()); // dir1/module1
            }
        };
    };
  4. Load your configs on starting up.

    startup.js

    const loader = require('candy-box');
    const path = require('path');
    
    loader(path.resolve('.')); // Assume you `candyboxrc.json` file is in the current path.