Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] Significant bundlesize increase with framer-motion@5 while using LazyMotion
See original GitHub issue1. Read the FAQs 👇
2. Describe the bug
With the upgrade to framer/motion@5 we’re seeing a significant bundle size increase. I understand that the new version offers lots of cool functionality so that there is an increase in bundle size could be expected. I wouldn’t expect his however when using LazyMotion,
| Page | Size old | Size new | Size diff | First load old | First load new | First load diff |
|---|---|---|---|---|---|---|
| / | 2.1kB | 2.1kB | 242kB | 249.0kB | +7kB🚨 | |
| /_app | 152kB | 164.0kB | +12kB🚨 | |||
| /[…url] | 4.3kB | 4.3kB | 260kB | 266.0kB | +6kB🚨 | |
| /404 | 6.4kB | 6.3kB | -0.1kB | 228kB | 235.0kB | +7kB🚨 |
| /about/[url] | 2.7kB | 2.7kB | 223kB | 230.0kB | +7kB🚨 | |
| /account | 15.0kB | 13.6kB | -1.4kB | 210kB | 220.0kB | +10kB🚨 |
| /account/addresses | 12.5kB | 9.8kB | -2.7kB | 220kB | 224.0kB | +4kB⚠️ |
We’re already using the LazyMotion feature and I would thus expect for the bundle size not too increase significantly.
4. Steps to reproduce
Steps to reproduce the behavior:
- Upgrade to framer motion 5
- See the difference in bundlesize
- See error
5. Expected behavior
Bundle size is not increased, and the additional features are loaded lazily
6. Video or screenshots
Not applicable
7. Environment details
Not applicable
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:11
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This fixed the issue! https://github.com/graphcommerce-org/graphcommerce/pull/1550#issuecomment-1180401005
@mattgperry this might be interesting https://github.com/vercel/next.js/issues/33394#issuecomment-1175900933