Alternative easing api and `edgeEasing` prop

[fritz-c]

Description

Instead of bundling in the d3-ease functions, the easing prop now accepts a callback that accepts functions of a form identical to d3-ease’s ease functions. That way those who want to customize their easing function can, those who want to use d3-ease’s functions can (and benefit from tree-shaking of the ones they don't use), and those who are happy with the default don't have to bear the extra weight of added d3 ease functions. And we get to sidestep all the d3 ESM mess. The README now includes a code snippet showing how users might use the new API.

As I was working on that, I noticed there was an old easing prop, edgeEasing that hadn't been addressed yet, so I added that in, too.

And as I was working on that, I noticed that there's a bit of an animation bug in that edge swipes result in the carousel flashing into its final position for one frame before starting the animation, so I added a kind of rough workaround for that.

Type of Change

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [?] Breaking change (fix or feature that would cause existing functionality to not work as expected) It would be a breaking change, save for the fact that we haven't released a version with easing available yet
• [x] This change requires a documentation update

How Has This Been Tested?

Manually

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
nuka-carousel	✅ Ready (Inspect)	Visit Preview	Sep 14, 2022 at 5:08PM (UTC)

[gksander]

I really like this approach. I think it's great to not burden all users with d3 bloat – and just allow users who do want to use d3 eases to provide it on their own.