motiondivision / motiondivision/motion
[BUG] "Reorder" is not compatible with "LazyMotion"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33.7k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 14
Description
1. Read the FAQs 👇
2. Describe the bug
Importing "Reorder" component makes "LazyMotion" useless, as the full features set (domMax) is included in the main bundle along with it.
The Docs:
"Because the normal motion component still preloads all of its functionality, including it anywhere will break the benefits of using LazyMotion."
However, it does not mention the similar behavior when using "Reorder". Also, <LazyMotion strict/> does not show any errors in the console when importing "Reorder" directly (without React.lazy)
5. Expected behavior
"Reorder" should be compatible with "LazyMotion" (being uninteractive until features load).
Alternatively, the Docs should mention this behavior.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with a direct Reorder import and , then inspect the Reorder and LazyMotion entry points and the bundle behavior. Confirm whether the full domMax feature set is included and whether strict mode reports it. Done means Reorder remains compatible with LazyMotion, or the documented LazyMotion guidance explicitly covers Reorder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100