remotion-dev/remotion







The issue has been solved
Old Node/FFMPEG version should trigger an error even when rendering via Node.JS APIs #1359
JonnyBurger posted onGitHub
š This issue is part of our Hacktoberfest campaign! š Read more about Hacktoberfest here š This issue is currently taken by @JRavi2!
Hacktoberfest Acceptance Criteria
- Currently in the CLI we check for the FFMPEG version: https://github.com/remotion-dev/remotion/blob/33668831b0335fcf1ff5580e53046dad97ff6273/packages/cli/src/validate-ffmpeg-version.ts#L8
- And for the Node.JS version: https://github.com/remotion-dev/remotion/blob/33668831b0335fcf1ff5580e53046dad97ff6273/packages/cli/src/check-version.ts#L16
- These checks should be moved into the
renderer
package so the warnings also appear when using the Node.JS APIs. - The Node.JS version should be immediately checked once the
@remotion/renderer
package is loaded. - The FFMPEG version should be checked before
renderMedia()
,renderFrames()
,getCompositions()
,stitchFramesToVideo()
gets called.