Motion error #34

Closed
opened 2026-10-14 17:48:23 +00:00 by Syndria98 · 2 comments
Owner

Error: Error

Invalid easing type 'ease-in'. For more information and steps for solving, visit https://motion.dev/troubleshooting/invalid-easing-type

Environment

  • runtime: node 24.21.0
  • my-bad: 0.2.11

Can you fix it?

## Error: Error ``` Invalid easing type 'ease-in'. For more information and steps for solving, visit https://motion.dev/troubleshooting/invalid-easing-type ``` **Environment** - runtime: `node 24.21.0` - my-bad: `0.2.11` Can you fix it?
Syndria98 added the ai-ready label 2026-10-14 17:48:23 +00:00
Agent added the working label 2026-10-14 17:50:32 +00:00
Collaborator

Fixed. The bug was in frontend/app/services/Tooltip.js: motion's animate() only accepts its own easing names (easeIn, easeOut, …), not CSS keywords, and the tooltip passed 'ease-in' / 'ease-out', which throws Invalid easing type 'ease-in'.

Changes

frontend/app/services/Tooltip.js

  • Line 22 (show): ease: 'ease-out' → ease: 'easeOut'
  • Line 36 (hide): ease: 'ease-in' → ease: 'easeIn'

The CSS ease-in-out declarations in ToastManager.vue and the ease transitions in <style> blocks are untouched — those are real CSS and valid.

Test

Added tests/motion-easing.test.js following the existing convention of reading frontend sources (no dependencies installed at repo root, like tests/map-viewer.test.js). It checks that the tooltip still has both ease options, that they are strings motion accepts, and that no frontend .js/.ts/.vue animation uses a CSS keyword as motion easing.

Ran node --test tests/ from the repo root: 73 tests pass, 0 fail (including the 3 new ones).

Fixed. The bug was in `frontend/app/services/Tooltip.js`: motion's `animate()` only accepts its own easing names (`easeIn`, `easeOut`, …), not CSS keywords, and the tooltip passed `'ease-in'` / `'ease-out'`, which throws `Invalid easing type 'ease-in'`. ## Changes **`frontend/app/services/Tooltip.js`** - Line 22 (show): `ease: 'ease-out'` → `ease: 'easeOut'` - Line 36 (hide): `ease: 'ease-in'` → `ease: 'easeIn'` The CSS `ease-in-out` declarations in `ToastManager.vue` and the `ease` transitions in `<style>` blocks are untouched — those are real CSS and valid. ## Test Added `tests/motion-easing.test.js` following the existing convention of reading frontend sources (no dependencies installed at repo root, like `tests/map-viewer.test.js`). It checks that the tooltip still has both ease options, that they are strings motion accepts, and that no frontend `.js/.ts/.vue` animation uses a CSS keyword as motion easing. Ran `node --test tests/` from the repo root: 73 tests pass, 0 fail (including the 3 new ones).
Agent referenced this issue from a commit 2026-10-14 17:52:38 +00:00
Collaborator

Implementation is ready for review: #37

Implementation is ready for review: https://git.aranroig.com/Syndria98/dragonroll/pulls/37
Agent added help wanted and removed working labels 2026-10-14 17:52:39 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Syndria98/dragonroll#34