Jacob

@gentunian Sorry it took so long, could you check if the problem happens in `3.14.x`? In #920, I fixed a bug with source maps that was causing the file path...

motion-canvas/core#21 presents a conceptual implementation by @schreiaj A few things off the top of my head: 1. `getBlob` is a really slow method. Using `ImageBitmap`s created via `createImageBitmap` would yield...

To start, I need to point out that the description of your PR is a bit misleading: > Create a render cache so scenes can render the UI quickly if...

I agree about the page on how motion canvas works. #202 will cover how to create your own components.

I think the best solution would be to turn `Gradient` into a node so that it could be placed in the scene: ```tsx const gradient = createRef(); view.add( ); ```...

If by "percentages of the parent" you mean its scale, then yes. After turning `Gradient` into a `Node`, putting it inside of another node would make it scale together with...

Agree. Also, I don't think there's a need to split them into separate files since they are more of a "write once, never edit" kind of thing, so we shouldn't...

Before I review the code, there are some major problems with the formatting, which lead me to believe that you didn't follow the contribution guide. Specifically the part about running...

It's hard to say but I think it's a good idea to upgrade. Looks like `@preact/preset-vite` already supports Vite 4, which is the only vite dependency we use. So it...

Thanks for the PR!