Coverage Report

This might be a really heavy breaking change, because some projects rely on a complete path to node-pg-migrate/bin/node-pg-migrate

We have one example in the docs:

So just FYI, please be aware of that we e.g. should have a compatibly layer or similar for this, so we don't break to many workflows out there.

That makes sense yeah, I am aware, actually I have tried babel and a few other use cases, I'm still going to test more stuff

❯ pnpm run babel create example

> [email protected] babel /npgm
> babel-node node_modules/node-pg-migrate/bin/node-pg-migrate.js "create" "example"

Created migration -- /npgm/migrations/1748716088549_example.js

yet, while I was trying ts-node, looks like the docs example does not work using latest node-pg-migrate?
just to confirm, but I think docs is wrong about this.

docs example:

{
  "scripts": {
    // ..
    "migrate": "ts-node node_modules/.bin/node-pg-migrate.js -j ts", 
  },
}

node_modules structure:

just to confirm, error:

> ts-node node_modules/.bin/node-pg-migrate.js -j ts "create" "test"

node:internal/modules/cjs/loader:1252
  throw err;
  ^

Error: Cannot find module './node-pg-migrate.js'
Require stack:

if you remove .js also won't work, we need the same script as the babel example which actually works.

> ts-node node_modules/node-pg-migrate/bin/node-pg-migrate.js -j ts "create" "test"

Created migration -- /npgm/migrations/1748717477579_test.ts

I'll test other cases to see if anything breaks with this change to src, but I think the priority rn is to finish the tests so I can get things working as they currently are and merge them. We can leave the bin changes for later, possibly as part of other related refactorings like #1137. I mainly did this because Vitest can't run coverage on the bin.

Closing this for now, will make something better with #1390 containers soon.