Upgrade lottie-web-vue 2.0.7 → 3.0.1
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 149
Description
# Upgrade lottie-web-vue 2.0.7 → 3.0.1 (major)
PR: https://github.com/FlowFuse/flowfuse/pull/8037
Dependabot opened a major bump for `lottie-web-vue`. Held from the weekly triage batch per major-bump policy — needs an owner and end-to-end verification.
## Risk assessment (low)
- Breaking change (lottie-web no longer bundled) only affects CDN `` consumers. FlowFuse is a bundler (webpack) user and already ships `lottie-web@5.12.2`, so this is a no-op for us.
- New `vue` peer dependency `^3.3.0` is satisfied by our `vue@^3.4.5`.
- No open advisories. Published via GitHub OIDC trusted-publishing with provenance (the "new releaser" is CI, not a compromised account).
## Verify before merging
- [ ] Named import `{ LottieAnimation }` in `frontend/src/main.js` still resolves — 3.x reworked the package exports (the changelog only promises the *default* import + `app.use()` plugin). Build the frontend and confirm `lottie-animation` registers and renders.
- [ ] Node engine: 3.x declares `engines.node: >=22`; repo declares `>=20.10.0`. No `engine-strict`, so Node 20 gives an EBADENGINE warning, not a failure. Fine on Node 24.
Contributor guide
Research direction
Start in frontend/src/main.js and inspect the named LottieAnimation import and registration. Update the dependency, build the frontend on Node 24, and confirm that lottie-animation registers and renders successfully with the 3.x package exports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100