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

prequelize

v3.0.0

Published

sequelize with less "features".

Downloads

198

Readme

Prequelize

sequelize with less "features".

Why

Sequelize has a clunky, promise API, and the where and include pattern is extremely dificult to follow, for no apparent reason.

Prequelize simplifies this significantly by not providing features that almost never get used.

Settings

the prequelize settings object is basically the same as the sequelize one, but with a simplified where and include syntax:

{
    // sequelize style settings...
    skip: 0,
    limit: 10,
    order: [['name', 'DESC']],

    // simplified where:
    where:{
        someField: 'x',
        relatedTable:{
            relatedField: 'y'
        }
    }

    // seperate, simple include:
    include:{

        // Either a list of included fields
        $fields: ['id', 'name', 'someField'],

        // Or keys, with a truthy value
        age: true,

        // With related tables nested.
        relatedTable: {
            $fields: ['relatedField']
        }
    }
}

API

All prequelize model methods take a callback as the last parameter, and return a righto.

If no callback is passed, the operation will not be run until the returned righto is run.

see righto for more info.

example:

Using normal callbacks:

    // Get a person with a callback,
    // Executes immediately
    prequelize.Person.get(
        123,
        {
            include: {
                $fields: ['firstName']
            }
        },
        function(error, person){

        }
    );

Using the returned righto:

    // Get a person righto, does not execute until used.
    var person = prequelize.Person.get(
            123,
            {
                include: {
                    $fields: ['firstName']
                }
            }
        );

    // Execute the query and get the resut.
    person(function(error, person){

    });

Get.

Get exactly one result by ID.

If no results are found, the call will be rejected with an Error with code 404.

get(id, settings, callback)

prequelize.Person.get(
    123,
    {
        where:{
            enabled: true
        },
        include: {
            $fields: ['firstName', 'surname']
        }
    },
    callback
)

Find.

Find the first result of a query.

If no results are found, the call will be resolved no result.

find(settings, callback)

Find All.

Find all results of a query.

findAll(settings, callback)

Find And Count All.

Find and count all results of a query.

findAndCountAll(settings, callback)

Find one.

Find exactly one result of a query.

If no results are found, the call will be rejected with an Error with code 404.

If more than one result is found, the call will throw.

findOne(settings, callback)

Find And Remove.

Remove all results of a query.

findAndRemove(settings, callback)

Remove One.

Remove exactly one result of a query.

If no results are found, the call will be rejected with an Error with code 404.

If more than one result is found, the call will throw.

findOneAndRemove(settings, callback)

Remove.

Remove exactly one result by ID.

If no results are found, the call will be rejected with an Error with code 404.

Create.

Create a record.

create(data, settings, callback)

Find One Or Create.

Find one or Create a record.

findOneOrCreate(data, settings, callback)

Bulk Create.

Bulk create records.

bulkCreate(data, settings, callback)

Find And Update.

Update all results of a query.

findAndUpdate(data, settings, callback)

Find And Update One.

Update exactly one result of a query.

If no results are found, the call will be rejected with an Error with code 404.

If more than one result is found, the call will throw.

findOneAndUpdate(data, settings, callback)

Update.

Update exactly one result by ID.

If no results are found, the call will be rejected with an Error with code 404.

update(id, data, settings, callback)

Update Many.

Update exactly the length of the ids array passed in.

If less than this is updated, the call will be rejected with an Error with code 422 (Unprocessable).

updateMany(ids, data, settings, callback)

Find One And Update Or Create.

Find one and Update or Create a record.

findOneAndUpdateOrCreate(data, settings, callback)

Count.

Count the number of results from a query.

Querying through associations

Given a through association like so:

project = { name, ... }
user = { name, ... }
projectUser = { canCreate }

you can just query the assiciation by name:

{
where: {
    name: 'project1',
    user: {
        name: 'bob',
        projectUser: {
          canCreate: true
        }
    }
}
}

Functions

db functions can be built with a simple expression syntax:

models.user.find({
where: {
    age: {
        $gte: 10
    }
},
include: {
    count: {
        $fn: 'count(col("id"))'
    }
}
});