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

database-updates

v4.1.0

Published

Apply database updates to your application based on semver file names

Downloads

1,000

Readme

database-updates

Apply database updates to your application based on semver file names

The purpose of this module is to ensure that all developers of an application have an up-to-date database. Arbitrary database update scripts or index creation scripts for new properties get created a lot, but all too often these scripts forget to be run which can result in an inconsistent state across developers and even environments.

Adding this module to your application will ensure that any scripts that need to be run will by executed across all machines during setup.

[!WARNING] TypeScript support is considered experimental. This module is written in JS but accepts update files that have a .ts file extension. It is dependent on your runtime being able to dynamically import() .ts files for it to work. Let me know if you have any problems with it and I can spend more time on it.

Installation

npm install database-updates

Usage

const { MongoClient } = require('mongodb')
const databaseUpdates = require('database-updates')

async function main() {
  const client = await MongoClient.connect(
    'mongodb://localhost/database-updates'
  )

  await client.db().dropDatabase()

  await databaseUpdates({
    db: client.db(),
    updatePath: `${__dirname}/test/fixtures/`,
  }).run()

  console.log('Done!')
  return client.close()
}

main().catch((e) => {
  console.error(e)
  process.exit(1)
})

const updates = new DatabaseUpdates(options)

Options must include:

  • db - a database connection returned from MongoClient.connect().db() or similar

Optional options:

  • updateCollectionName - the collection to store app updates. Defaults to databaseUpdates
  • updatePath - the location to look for update scripts. Defaults to process.cwd() + '/updates'
  • logger - the logger to use. Defaults to console

Returns:

  • updates - an array of update files that were run

An update script

An update script is a JavaScript file with the following signature:

// ESM
export default function (db) {}
// CJS
module.exports = function (db) {}

This can be an async function, or return a Promise.

The db parameter is your application's database object. This enables you to modify the database.

An example update script to add an index to a collection would be:

// ESM
export default (db) => {
  return db.collection('a').createIndex({ a: 1 })
}
// CJS
module.exports = (db) => {
  return db.collection('a').createIndex({ a: 1 })
}

When an update script is run once, it will never be run again on the same machine. The files that have been applied are stored in the (configurable) databaseUpdates collection.

Naming

The naming of update scripts is significant for the order in which they are run. The first part of the filename must be a valid semver version e.g. 0.0.1-adding-first-admin-user.js. The second part (after the '-') is a description of the update.

A folder with the following update scripts:

1.0.0-update.mjs
1.0.2-update.mjs
1.0.3-update.ts
0.0.1-update.js
0.0.2-update.js

Would get run in this order:

0.0.1-update.js

0.0.2-update.js

1.0.0-update.mjs

1.0.2-update.mjs

1.0.3-update.ts

Credits

Dom Harrington

KeystoneJS - for the concept