[Question]: Possible consideration for NodeJS support again due to alternatives going away?

[jonbarrow]

I have read the FAQ and seen the reasons for dropping NodeJS support, and I definitely do understand that it is a lot of extra effort to do so, however the FAQ is now outdated and the given solutions are no longer viable. One of the two given reasons for not supporting NodeJS in this library is that there are alternatives elsewhere, however the alternatives given are all deprecated and no longer being maintained:

• https://www.npmjs.com/package/fluent-ffmpeg - Archived May 22, 2025 and directly says it's no longer usable right now: This library is no longer maintained and no longer works properly with recent ffmpeg versions. Use it as your own risk, this repository is readonly and does not accept issues or PRs.
• https://github.com/arthenica/ffmpeg-kit - Archived June 23, 2025 and states that existing binaries will be removed in the future, though it seems like it's still working until then: FFmpegKit has been officially retired. There will be no further ffmpeg-kit releases. All previously released ffmpeg-kit binaries will be removed

ffmpeg.wasm now seems to be the last actively maintained ffmpeg library for the JS ecosystem from what I can see. Even ffmpeg.js seems largely abandoned (it has not been archived but the last commit was 4 years ago and issues are piling up without response from the maintainers, and it seems like new people are having issues even getting it built)

Given the state of the ecosystem, is it possible to consider adding NodeJS support back into the roadmap for ffmpeg.wasm? I know the FAQ states that PRs are welcome for this, but I'm wondering about direct support from the maintainers here given that everything else seems to be closing up shop. To be clear I'm not asking for any sort of quick fix or time frame or anything, just wondering about if it's something you'd even consider adding back to the roadmap officially