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

lib-loader

v0.5.1

Published

load and cache libraries and configs using the require system for easy access

Downloads

37

Readme

lib-loader

This is a small module for making library and config loading 100x easier but mostly just less verbose.

Cache your libs

This is an example library structure

|_ index.js
|_ libRunning.js
|_ systemLib/
    |_ settings.json
    |_ awesome_system_module/
        |_ index.js

Place this statment where ever you want to first cache your library. You can only call this once per library otherwise you will recieve an error.

// index.js
require('lib-loader').load({
    // this is the directory your library files reside
    libDir: './systemLib', // defaults to process.cwd()+'/lib'

    // this is the key the library will be cached under
    libKey: 'system', // defaults to 'lib'
});

Use your libraries

You can access your cached libraries by using this statment. Notice I use the .system attribute. This is determined by the value we place in libKey. All files and folders are required and cached under require('lib-loader') for easy access.

// libRunning.js
var system = require('lib-loader').system;
system.settings // equivalent to the return of require('./systemLib/settings.json')
system.awesome_system_module // equivalent to the return of require('./systemLib/awesome_system_module/index.js');

Load many libraries

If you are like me you may have several libraries to load.

require('lib-loader').loadMany([
    { libDir: 'systemLib',  libKey: 'system' },
    { libDir: 'webLib',     libKey: 'web' },
    { libDir: 'systemLib2', libKey: 'system2' }
]);

Exluding files

Exclude files using globs checkout minimatch for what is possible.

require('lib-loader').load({
    libDir: './lib',
    libKey: 'lib',
    exclude: [
        '*.json',
        'iDontWantToLoadThis.js'
    ]
});

Checkout the tests directory for a real example.