Many updates during transitions, future plans

[gurkerl83]

I am experimenting with the codehike source, especially with the Scrollycoding component and its subcomponents.

The component EditorSpring and, more specifically, in the hook useStepSpring, another hook useSpring gets used, providing the progress. The progress property is passed down to all components down to the very leaves; when a transition executes, a ton of updates get triggered. The progress or t property gets used quite frequently in those sub-components. My question here is; is it possible to separate transitions used in the editor, its subcomponents, and the content components like SmoothLines?

A lot is going on in the respective components, and a vital requirement for memoization. The combination of tons of updates makes it hard for me to contribute.

Animation is complex, and the use case is large, with many variants. In terms of animation, maybe other libraries can help using certain features which are very hard to come up with otherwise, such as framer-motion. Before I invest too much time, do you have a rough roadmap and future plans for codehike. I saw your bright repository using sever components to reduce or eliminate increases in the bundle size of a page. Maybe you can clarify the priorities of those two projects and or plans to integrate one into another.

Also, the bundle size of codehike adds some pretty extra load; in my case, it is about 100KB, but sure is used only in some places, only when you show code snippets.

Thx!