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

@moifort/fireway

v1.0.5

Published

Schema migration tool for Firestore

Downloads

2

Readme

fireway

A schema migration tool for firestore heavily inspired by flyway

Install

yarn add --dev @moifort/fireway

How to

Run on emulators: fireway migrate --path=MIGRATION_DIR_PATH --projectId=FIREBASE_PROJECT_ID --emulator

  • MIGRATION_DIR_PATH: migration directory path where script are see Migration file format. i.e. ./migration/dev
  • FIREBASE_PROJECT_ID: firebase project id defined in .firebaserc file. i.e. grdf-c590f

On production: fireway migrate --path=MIGRATION_DIR_PATH

CLI

Usage
  $ fireway <command> [options]

Available Commands
  migrate    Migrates schema to the latest version

For more info, run any command with the `--help` flag
  $ fireway migrate --help

Options
  -v, --version    Displays current version
  -h, --help       Displays this message

fireway migrate

Description
  Migrates schema to the latest version

Usage
  $ fireway migrate [options]

Options
  --path         Path to migration files  (default ./migrations)
  --projectId    Target firebase project
  --emulator     Run on emulator
  -h, --help     Displays this message

Examples
  $ fireway migrate
  $ fireway migrate --path=./my-migrations
  $ fireway migrate --projectId=my-staging-id

Migration file format

Migration file name format: vXXX__[description].js when XXX is a number ex: 001, 002

// each script gets a pre-configured firestore admin instance
module.exports.migrate = async ({firestore}) => {
    await firestore.collection('name').add({key: new Date()});
};

Migration results

Migration results are stored in the fireway collection in firestore


{
  checksum: 'fdfe6a55a7c97a4346cb59871b4ce97c',
  description: 'example',
  execution_time: 1221,
  installed_by: 'system_user_name',
  installed_on: firestore.Timestamp(),
  installed_rank: 3,
  script: 'v0.0.1__example.js',
  success: true,
  type: 'js',
  version: '0.0.1'
}

Migration logic

  1. Gather all the migration files and sort them according to semver
  2. Find the last migration in the fireway collection
  3. If the last migration failed, stop. (remove the failed result or restore the db to continue)
  4. Run the migration scripts since the last migration

Authentication

To run on your project (with your CD for instance) give GOOGLE_CREDENTIALS environment variable.

GOOGLE_CREDENTIALS='{ "type": "service_account", "project_id": "...", "private_key_id": "...", "private_key": "...", "client_email": ...", "token_uri": "..." }' fireway migrate --path=./migration/prod

You can find the json on your firebase console: Settings/Service Account/SDK Admin Key/Generate private key

You dont need GOOGLE_CREDENTIALS if you use --emulators but you must provide --projectId

Thanks

@kevlened