Tsvetan

No problem! It seems to depend on the height of `AspenFileTree`, e.g. with 700 in the example above it errors at key 24. And it does happen in my app...

After some experiments I have pinpointed it to [FileTree.tsx - getItemAtIndex](https://github.com/NeekSandhu/react-aspen/blob/630f7c0f0ae3923c27c0af02f589a841678e5c00/src/components/FileTree.tsx#L330). If I bypass the `idxTorendererPropsCache` map, I see that at some point different items are returned for the same...

I think so. My interpretation is that when a directory is unfolded (due to ensureVisible), the elements in the list change their index.

I use it too, like it very much. However with RC5 there is a problem only in production build, and I am not sure whether it's Angular or build-specific problem....

I think [catmullRom](https://en.wikipedia.org/wiki/Centripetal_Catmull%E2%80%93Rom_spline) looks much smoother. Even though there are no plans for adding more curve options (#821), how feasible is it to change the interpolation algorithm behind `smooth`?

I've hit the same, thanks for submitting this issue 😅 It would be nice (apart from supporting `float`) to improve the "this should never happen" error and mention that this...