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

@alifar/dbver

v1.0.8

Published

Migrate postgresql database based on the files

Downloads

20

Readme

Database versioning and migration based on the files that you specified.

Currently works for PostgreSQL.

Important Notes

  1. There must be a 'version' folder in root of the project and all sql files must be placed in. The standard format for the naming can be: version-001.sql, version-002.sql, etc.
  2. you must set all postgres connection string variables as .env file in root of the project. These constant variables are:
  • POSTGRES_SERVER
  • POSTGRES_PORT
  • POSTGRES_USER
  • POSTGRES_PASSWORD
  • POSTGRES_DB

All you have to do is require the module

require('@alifar/dbver');

More Detail

In order to use this module:

  1. Create the folder with name version in the root of your project Add "version" folder to the root
  2. Create the sql versioning file with the pattern version-001.sql, version-002.sql, ... under the version folder. Each file contains sql statement steps during the project progress. Each statement in each file must be end with semicolon ';' and it is important to follow this rule. Add semicolon at the end of each statement
  3. you can add the .env file in root of project and all POstgreSQL configurations must be set there. It is recommanded that use dotenv module for managing the environment variables. The keys are as follows:
  • POSTGRES_SERVER
  • POSTGRES_PORT
  • POSTGRES_USER
  • POSTGRES_PASSWORD
  • POSTGRES_DB Add environment variables
  1. You can add the code bellow on seperate file like versioning.js and add the command at scripts section in package.json file.
require('@alifar/dbver');

Add to scripts section in package.json

  1. Now you can run script each time the new version file add to the project
npm run-script mig