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

voila-fs-di

v1.0.1

Published

A library for creating a di graph from modules on the file system

Downloads

9

Readme

Voilà File System Dependency Graph

Build Status Code Climate Test Coverage

A library for creating a DI graph from modules on the file system

Common usage, with main.js as follows.
If using a build step, the globs should be written to be correct in the transpiled code

const promise = fsGraph({
  globs: [
    `src/controllers/**/*Controller.{js,ts}`,
    `src/daos/**/*Dao.{js,ts}`,
    `src/services/**/*Service.{js,ts}`
  ],
  deriveKey: func => func.name
});

And with the file system arranged as follows.

root
 └─┬src
   ├─┬controllers
   | └──resourceController.js
   ├─┬daos
   | └──resourceDao.js
   ├─┬services
   | └──resourceService.js
   └──main.js

And with the file contents as follows.

resourceController.js

export default function resourceController(resourceService) {

  return {
    doControllerAction(request, reply) {
      // [... transport logic]
      return resourceService.doServiceAction(request.params).then(reply);
    }
  };
}

fsGraph expects that modules that match the glob patterns export a function as module.exports or default. Each function is passed to the deriveKey option to determine its di key. The function arguments are parsed and should coincide with the other keys in the graph--this does not work with transpiled destructuring.

resourceService.js

modules.exports = function resourceService(resourceDao) {

  return {
    doServiceAction(params) {
      // [... business logic]
      return resourceDao.doDaoAction(params);
    }
  };
}

resourceDao.js

export default function resourceDao(/* someClient */) {

  return {
    doDaoAction(params) {
      // [... dao logic]
      // someClient.send(params);
    }
  };
}

This setup will produce a dependency graph, for use with voila-di, as follows.

import fsGraph from 'voila-fs-di';

const promise = fsGraph({
  globs: [
    `src/controllers/**/*Controller.{js,ts}`,
    `src/daos/**/*Dao.{js,ts}`,
    `src/services/**/*Service.{js,ts}`
  ],
  deriveKey: func => func.name
});

promise.then(console.log);

// { resourceController:
//     { dependencies: [ 'resourceService' ],
//       provider: [Function: resourceController] },
//   resourceDao:
//     { dependencies: [],
//       provider: [Function: resourceDao] },
//   resourceService:
//     { dependencies: [ 'resourceDao' ],
//       provider: [Function: resourceService] } }

And this is what the integration looks like.

import fsGraph from 'voila-fs-di';
import di      from 'voila-di';

const promise = fsGraph({
  globs: [
    `src/controllers/**/*Controller.{js,ts}`,
    `src/daos/**/*Dao.{js,ts}`,
    `src/services/**/*Service.{js,ts}`
  ],
  deriveKey: func => func.name
});

promise
  // Validate here if you'd like
  .then(graph => di(graph).get('resourceController'))
  .then(console.log);

// => { doControllerAction: [Function: doControllerAction] }