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

pg-migration-manager

v1.0.12

Published

The super simple migration manager for pg driver.

Readme

Image alt

The super simple migration manager for loved by everyone pg driver.

Installation

npm i pg-migration-manager

Importing

import MigrationManager from 'pg-migration-manager';

Usage

import * as http from 'http';
import { Pool } from 'pg';
import MigrationManager from 'pg-migration-manager';


class Server { 
    server;
    database;    

    initServer(){
        this.server = http.createServer((req, res)=>{/** request handling **/})
    } 

    async initDatabase(){
        this.database = new Pool(/** connection config **/);

        const manager = new MigrationManager(this.database, {
               pathToMigrations: 'src/migrations', // required
               migrationTableName: 'migration', // optional
           });
        
        await manager.runMigrations();
    }
    
    async start(){
        this.initServer();
        await this.initDatabase();
        this.server.listen(3000, 'hostname');
    }   
}

new Server().start().then(()=>'server has started')

The most reasonable way to implement migrations is to run sql scripts before server has started.

First you create instance of MigrationManager class passing to it database client and configuration object.

The last one contains:

  • pathToMigrations - a path to a folder where your sql scripts store.
  • migrationTableName - a name of a table that will be created for writing fulfilled migrations.

Then you execute runMigrations method that's returning promise.

During the runMigrations method runtime there will create migration table in database (if it does not exist yet), then your migrations will be worked out and written in this table.

Next time when you start server saved migrations will be ignored, only new ones will be run.

Note: thus don't change migration file names.

Another note: the migration manager implements migrations one by one according to creation dates of files.

In conclusion

I'll be happy to hear your ideas and suggestions to possible improving this tiny but helpful tool.