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 🙏

© 2025 – Pkg Stats / Ryan Hefner

flyway-validator

v1.2.2

Published

Basic validation for flyway script directory

Readme

Flyway migration script validator

This is a simple package that will validate a few facts about the flyway migrations cripts in a provided directory as a sanity check.

Usage

Install with

npm install --save-dev @nw/flyway-validator

or

npm install --save-dev @nw/flyway-validator

then just scan any directory containing flyway scripts

npx @nw/flyway-validator path/to/directory

If everything is ok, the process will complete with an exit code of 0, otherwise it will exit with an error and display a (hopefully) helpful message explaining what it thinks is the problem.

It is recommended to add this check to a pre-commit hook or something so that you dont have to think about it.

What is checked

  • The first file is versioned as 1.0.0, 0.1.0, 0.0.1

  • The files version numbers are dates are both in the same sequence

  • The sequence numbers do not skip any version, ie a jump from 1.0.0 to 2.3.0 is invalid

  • No files have beem modified since the last commit

What is not checked

ANYTHING ELSE!

no sql validations, no schema validations, no model or business logic, that is all up to you. This is seatbelt, you still have to drive safely!