The idea of index.embed.js  is to allow you to host multiple animations without needing to load multiple copies of Core on the same page. It’s a much smaller file, suited to some sorts of use cases (e.g. legacy web apps that don’t use modern build tooling) and less likely to crop up in a brand new app built off today-standard JS framework. 

We also provide index.standalone.js —which bundles a copy of Core along with the animation for a situation where you need to put exactly one animation on a page for some reason. 

We don’t expect these to be common use cases, but they’re supported.

Did this answer your question?