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

@olemop/loader

v0.0.49

Published

Load codes for olemop based on the convention over configuration rules.

Downloads

8

Readme

@olemop/loader - loader module for olemop

Load codes for olemop based on the convention over configuration rules.

@olemop/rpc could load modules in batch but not load the sub-directory recursively.

Regulation

  • Module name

Module would use the filename by default. For example: load lib/a.js and the return result would be: { a: require('./lib/a') }

It would use the name if the module with a name property. For example

// a.js
exports.name = 'test'

the return result would be: { test: require('./lib/a') }

  • Module definiation

If the module exported as a function, @olemop/loader would take it as a factory method and generate a new instance of module by calling the function. And it would return the module directly for other situation.

module.exports = (context) => {
  // return some module instance
  return {}
}

Installation

npm install @olemop/loader

Usage

const Loader = require('@olemop/loader')

const res = Loader.load('.')

console.log('res: %j', res)

API

Loader.load(path, context)

Load all modules in the path.

Parameters

  • path loaded path
  • context if the module provides a factory method, the context would be pass as a parameter as the factory method.