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

@datawrapper/orm

v3.22.3-ssl3

Published

A database abstraction layer for Datawrapper

Downloads

194

Readme

datawrapper-orm

A database abstraction layer for Datawrapper

Usage:

Add the package to your repository using:

npm i --save "@datawrapper/orm"

In your app you need to initialize the ORM before you can do anything else with it. It's a good idea to do this in your apps main entry point:

const orm = require('@datawrapper/orm');

orm.init({
    dialect: 'mysql',
    host: '127.0.0.1',
    port: 3306,
    user: '...',
    password: '...',
    database: '...'
});

Then you can load the models using:

const { Chart, User } = require('@datawrapper/orm/models');

Note that this will initialize the entire model, which assumes that your database user has access to all the database tables. If this is not the case you can load individual models using

const User = require('@datawrapper/orm/models/User');

Plugins

The ORMs functionality can be extended with plugins. This is needed, for example, when new database tables are needed. The plugin API follows the convention of plugins in datawrapper/api.

A simple ORM plugin that does nothing looks like this:

/* config.js */
plugins: {
    'my-orm-plugin': {
        my_name: 'Steve'
    }
}

/* orm.js */
module.exports = {
    register: async (ORM, config) => {
        console.log(`Hi I am ${config.my_name}!`)
        // logs "Hi I am Steve!" on registration
    }
}

There are 2 interesting properties on the ORM object that help with plugin access.

  • ORM.plugins is an object with all configured plugins. They are not registered by default. Since standard Models are not defined after ORM.init() either, it wouldn't make sense to do that for plugins.

This is how you register a plugin:

await ORM.init()
const { plugins } = ORM

const MyORMPlugin = require(plugins['my-orm-plugin'].requirePath)
await MyORMPlugin.register(ORM, plugins['my-orm-plugin'])

This method is very useful for tests where you only need a special plugin. There is also a helper method to register all plugins. It is in functionality similar to requiring all models with require('@datawrapper/orm/models').

  • ORM.registerPlugins will register all plugins.
await ORM.init()
await ORM.registerPlugins()