Flame Engine flame_svg-v2.0.0 Released
Flame SVG v2.0.0 is a breaking release aimed at keeping the package aligned with current Flutter while tightening up SVG handling. The headline change is the removal of Svg.integralSize: that behavior is now always enabled, so any code that relied on disabling it will need to be adjusted during migration.
The release also adds cache parameters/properties to Svg to prevent cache thrashing. In practice, that should make repeated SVG use more stable and predictable, especially in projects that load or swap vector assets frequently. For teams using SVGs in UI, icons, or in-game overlays, this is the kind of change that can reduce unnecessary churn and help avoid performance hiccups.
Compatibility with Flutter 3.47 is another important part of the update. That makes this version less about new features and more about keeping Flame SVG usable on the latest Flutter toolchain without forcing downstream projects to pin older dependencies.
Because this is a 2.0.0 release with explicit breaking changes, developers should expect a small migration pass rather than a drop-in upgrade. The main thing to check is any code touching Svg.integralSize, followed by whether the new cache controls need to be tuned for a project’s asset-loading pattern.
“This release has breaking changes.”
- what
- Flame SVG v2.0.0 released with breaking changes.
- what
- Svg.integralSize was removed and its behavior is now always true.
- what
- New cache parameters/properties were added to Svg to prevent cache thrashing.
- what
- The package was updated to adapt to Flutter 3.47.
Useful fixes, but the breaking API change requires migration.
Follow flame engine updates
See relevant stories in your personalized news feed.
Discussion