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 🙏

© 2026 – Pkg Stats / Ryan Hefner

loopback-extended-lib

v0.5.2

Published

LoopBack Extended Lib

Readme

Loopback Extended Lib

Build Status Coverage Status

Extend Loopback in random ways, and put everything in a lib.

See the example for a full functioning Loopback project.

What's included

The idea

For a single project, we have:

  • A single lib.
  • A single app, which must be at lib.app, and can be used anywhere (with a lib = require('path/to/lib')).
  • The app has a root directory that never changes, and it can boot() itself.

The "lib"

You usually have a lib directory in your project, with an index.js file in it, which would look like:

// The lib.
const lib = require('loopback-extended-lib');
// Register files.
lib.register(__dirname);
// Export.
module.exports = lib;

It can register files multiple times, and the same files would be overridden. For more details, see file-register

The "extended"

  • lib.extended.loopback() can be used to generate an app, which is supposed to be used exactly once for one project. See the example for more details.
  • app.boot() can be used to boot the app, which will only boot once (multiple calls would return a cached promise).
  • app.reboot() can be used to "reboot" the app. Usually it's only used in tests. Be careful that this can break the connections to the data sources.

The "vars"

Some global variable getters/generators that are usually useful. For more details read the source code - they are short.

  • lib.vars.debugging() can tell if we are in the debugging mode.
  • lib.vars.namespace() can build a string in the format [project namespace]:[local namespace], similar to what people usually use with the debug module, and is usually used in debug and log etc.