FAQs
Must every module be passed to kd.use() before I animate?
Usually, yes. If the core arrives through a plain <script> tag rather than a bundler, Kinedrift will try to wire modules up on its own the moment they land, but we still suggest declaring them so that dead-code removal never strips a module nobody appears to reference. You can hand the whole set over in a single call, like so
kd.use(ScrollTrack, PathTrace, TypeSplit);
Does calling use() twice on one module cause trouble?
No. Registration is idempotent — the second call sees the module already on the registry and returns straight away, so repeating it across files costs nothing but a lookup.
My editor flags a missing type declaration — what now?
Point the compiler at the bundled declaration folder rather than the source tree, then reload the language server. Editors cache the old resolution and will keep reporting the error until they restart.
How can I load the UMD build of Kinedrift through a bundler?
Import from the /umd/ folder inside the package instead of the package root. Every module ships in both formats, so the paths stay identical apart from that one segment.
Why does my production bundle break once tree-shaking runs? (only in release builds)
Almost always a module that was pulled in for its side effects but never registered. Mark the package as side-effectful in your build config, or register the module explicitly, and the release build will match your development one.
Can I stay on an older release line?
Yes — every published line stays installable by pinning its exact version. Security patches land on the two most recent lines only, so plan an upgrade window if you sit further back than that.