Plans for v8 (Node v20+, esm-only)

[Shinigami92]

While trying to support esm alongside cjs, more and more issues popping up 😢

I think the time has come to move forward and leave the cjs world behind. node-pg-migrate is also mostly anyways a CLI tool, and so hopefully it wont hurt the community that much.
However, as a first pre-step I setup a v7 branch, where in worst case we can e.g. backport features if possible.

Together with esm-only support, I will also remove support for Node v18, because import.meta.dirname is only a thing since Node v20.11.0.

Additionally TypeScript v4 support will be dropped.

Feel free to start some discussions below and provide feedback or help.

[JakubGodlewski1]

So when do you plan to release the changes/v8?

[Shinigami92]

So when do you plan to release the changes/v8?

Not sure at all, but it could even be after Node v18 reached EOL -> April 2025

[Shinigami92]

A first experimental release is available at https://www.npmjs.com/package/node-pg-migrate/v/8.0.0-experimental-1328-1 containing the commit 4e91913 from #1328.
Please report all bugs to that PR.

• chore!: drop cjs support #1328

[Shinigami92]

There is already a working https://github.com/salsita/node-pg-migrate/releases/tag/v8.0.0-rc.0

However I'm thinking about to wait for TS 5.8 and its erasableSyntaxOnly feature. Also I could still wait for official Node v18 drop, because there is theoretically now rush needed to immediately release it.
Additionally there might still be some things in the documentation that is off now. Feel free to help and contribute if you found something like that. I appreciate help from the community 🙏