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

barrels-as-promised

v0.0.2

Published

A Promise wrapper around the barrels utility

Downloads

11

Readme

barrels-as-promised

A Promise wrapper around the barrels utility.

Build Status

Installation

npm i --save-dev barrels-as-promised

Usage

NOTE: Adapted from the Barrels docs. Everything described there holds true here with the added promisy goodness described below...

Drop your fixtures in test/fixtures as JSON files (or CommonJS modules) named after your models.

Once your Sails.js server is started:

var Barrels = require('barrels');
var barrels = new Barrels();
var fixtures = barrels.data;
barrels.populate()
  .then(function() {
    // do stuff
    ...
  })
  .catch(function (err) {
    // oops
  });

Pass to the constructor the path to the folder containing your fixtures (defaults to ./test/fixtures).

Populateing the test database involves three steps:

Removing any existing data from the collection corresponding to the fixture Loading the fixture data into the test database Automatically applying associations (can be disabled by passing false as the last parameter to populate) Populate also accepts an array of names of collections to populate as the first (optional) argument, for example:

barrels.populate(['products'])
  .then(function() {
    // Only products will be populated
    ...
  });

Automatic association

Use the number of position (starting from one) of an entry in the JSON fixture as a reference to associate models (see https://github.com/bredikhin/barrels/blob/master/test/fixtures/products.json for example). This feature can be disabled by passing false as the last parameter to populate.

Required associations

If you have any associations described as required: true, they will be added automatically, no matter if the last parameter to populate is false or not. However, you have to load your fixtures gradually (by passing an array of collection names as the first parameter) in such an order that collections corresponding to the required associations get populated first.

Let's say, for example, you are implementing a Passport.js-based authentication, and every Passport has User as a required association. You'd write something like this:

barrels.populate(['user', 'passport'])
  .then(function() {
    // Do your thing...
  });

Dependencies

License

The MIT License