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

waterline-model-loader

v0.2.8

Published

Load Waterline models from a directory

Readme

Waterline model loader

npm version Build Status Coverage Status Dependency Status devDependency Status

Node module to load Waterline models from a directory and use the file names (without the extension) for the model names. It is an abstraction on the Waterline loading process.

Installation

npm install --save waterline-model-loader

Basic usage

Create a directory where your models live. The files are loaded recursively, however the name of the model files must be unique.

Model example:

// ./models/Example.js

// A regular Waterline model
module.exports = {
    attributes: {
        name: {
            type: 'string',
            required: true
        }
    }
};

Usage example:

const path = require('path');
const modelLoader = require('waterline-model-loader').default;

let config = {
    modelsDir: path.join(__dirname, './models'),
    connections: {
        // Waterline connections object
    }
};

modelLoader.setup(config).then(models => {
    // do stuff with your Waterline models
    let ExampleModel = models.Example;

    // do stuff with ExampleModel
}).catch(err => {
    // deal with any setup errors
});

// Alternatively you can access the models from the modelLoader singleton after setup:
// let models = modelLoader.models;


// When quiting your app you can teardown the connections.
// This could be necessary for tests if multiple connections are loaded.
modelLoader.teardown().then(() => {
    console.log('done');
}).catch(err => {
    // deal with an error (and report it if you suspect a bug)
})

See the Waterline docs for a connections object or check the tests for an example.