Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Shinigami92 opened this issue Aug 31, 2024 · 2 comments
Open

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

Shinigami92 opened this issue Aug 31, 2024 · 2 comments
Assignees
Labels
breaking change Cannot be merged when next version is not a major release
Milestone

Comments

@Shinigami92
Copy link
Collaborator

Shinigami92 commented Aug 31, 2024

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.

@Shinigami92 Shinigami92 added this to the v8.0 milestone Aug 31, 2024
@Shinigami92 Shinigami92 self-assigned this Aug 31, 2024
@Shinigami92 Shinigami92 pinned this issue Aug 31, 2024
@Shinigami92 Shinigami92 added the breaking change Cannot be merged when next version is not a major release label Aug 31, 2024
@JakubGodlewski1
Copy link

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

@Shinigami92
Copy link
Collaborator Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Cannot be merged when next version is not a major release
Projects
None yet
Development

No branches or pull requests

2 participants