Chapter 304: v5.0 Migration

Core Idea

:::note Remotion 5. 0 is not yet released.

Key Concepts

• How to upgrade
• Runtime requirements
• Telemetry is now mandatory for Company License customers
• WebGL and WebGPU during rendering are now enabled by default
• selectComposition() and getCompositions() now require inputProps
• bundle() and getCompositions() now take an options object
• visualizeAudio() yields different result
• TransitionSeries does not support layout="none" anymore

Code Examples

- "remotion": "4.0.141"
- "@remotion/bundler": "4.0.141"
- "@remotion/eslint-config": "4.0.141"
- "@remotion/eslint-plugin": "4.0.141"
- "@remotion/cli": "4.0.141"
- "@remotion/renderer": "4.0.141"
+ "remotion": "5.0.0"
+ "@remotion/bundler": "5.0.0"
+ "@remotion/eslint-config": "5.0.0"
+ "@remotion/eslint-plugin": "5.0.0"
+ "@remotion/cli": "5.0.0"
+ "@remotion/renderer": "5.0.0"

• What it demonstrates: Usage pattern for v5.0 Migration from the official docs.

Key Takeaways

1. Understand how to upgrade when working with v5.0 Migration.
2. Understand runtime requirements when working with v5.0 Migration.
3. Understand telemetry is now mandatory for company license customers when working with v5.0 Migration.
4. Understand webgl and webgpu during rendering are now enabled by default when working with v5.0 Migration.
5. Understand selectcomposition() and getcompositions() now require inputprops when working with v5.0 Migration.

Connects To

• 2 0 Migration: related page in the Migration & Versioning section.
• 3 0 Migration: related page in the Migration & Versioning section.
• 4 0 Migration: related page in the Migration & Versioning section.