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

@zulus/migrations-runner

v1.0.0

Published

Runner for SQL migrations, using Knex module

Downloads

4

Readme

migrations-runner

pipeline status coverage report

Applied migrations, that stored in a dir, using Knex query builder.

npm i @zulus/migrations-runner

Structure

USAGE

in console

./node_modules/.bin/migrations_runner -d ./src/migrations

API

runMigrations(knex, dirname, [options])

Applied migrations, stored at dirname in files, with name in format<timestamp>-<name>.sql

  • knex - The Knex instance
  • dirname -The absolute path to directory with migrations
  • options
    • src - list of migrations, that should be used
    • last - last date of migrations

CLI

Write next lines in your console, to view documentation for CLI tool

runMigrations --help

Contributing

To start contributing do

git clone [email protected]:ZulusK/nodejs-migrations-runner.git
git checkout develop
git checkout -b <your-branch-name>

The project is developed in accordance with the GitFlow methodology.

What it means
  1. All work you should do in your own local branch (naming is important, look below), then make pull request to develop branch
  2. Your local branch should not have conflicts with repository develop branch. To avoid it, before push to repository, do:
    git pull origin develop
    # resolve all conflicts, if they exists
    git add --all
    git commit -m "fix conflicts"
    git push origin <your-branch-name>
  3. We use next naming of branches:

| branch template | description | | ------------------------------------ | ----------------------------------------------------------- | | feat/<short-feature-name> | new feature, ex. feat-add-logger | | fix/<short-fix-name> | fix of existing feature, ex. fix-logger | | refactor/<short-scope-description> | refactor, linting, style changes, ex. style-update-eslint | | test/<short-scope-descriptiopn> | tests, ex. test-db-connections | | docs/<short-scope-descriptiopn> | documentation, ex. test-db-connections |

Important, before push
  1. We use eslint with this rules to lint code, before making pull request, lint your code:

    npm run lint
  2. Before making pull request, run tests

    npm run test