-
Notifications
You must be signed in to change notification settings - Fork 880
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
Announcement: roadmap for fluent-ffmpeg v3 #1233
Comments
Amazing! Thanks a lot 💪 |
Great, we need this repo to live long. I am willing to contribute let me know if i can pick something. I am using this library in one of my projects. I hope many people still use it. |
It's a really helpful tool to handle ffmpeg. I hope it will get the maintenance it deserves. |
Is this still in plans? Or we better not expect changes in the API and stick to the v2? |
Yep. It's late, as always, due to real life stuff :) |
hello, thanks for your work on it! It is possible to provide v3 as beta tagged in npmjs ? At least, we can already work on it without rebuilding on our side. but anyway thanks ! |
There will be an alpha as soon as it is usable |
What is the status of plans to add types? I'd love to help with any TypeScript questions but I'm not familiar with this library yet. I want to be and TypeScript would help a lot. |
Looks like they're on DefinitelyTyped https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/fluent-ffmpeg |
Hey there,
I'm planning to do a bunch of maintenance on this package and publish a version 3 in the coming weeks, hopefully before 2024.
The codebase is now pretty old and it is long overdue for some refactors.
Here is a rough outline of what version 3 will include. This is not a commitment, just a bunch of ideas.
This will most likely introduce incompatibilities with code using version 2. As a consequence when v3 is released I will probably close all existing pull requests (some of them will be merged first, when they make sense).
The project is still lacking long-term maintainers and workforce to triage and answer issues. There have been some proposals in #755 but unfortunately they came at times where I was not really involved on the project nor watching answers, so if some of you reading this feel up to the task, drop a comment there.
The text was updated successfully, but these errors were encountered: