airbnb
Repos
195

JavaScript Style Guide

131234
22197

Render After Effects animations natively on Android and iOS, Web, and React Native

33556
5191

An iOS library to natively render After Effects vector animations

23662
3350

render React components to Sketch ⚛️💎

14947
815

Events

Created at 23 minutes ago
Created at 31 minutes ago
Created at 51 minutes ago
opened issue
3.7

How to use it?

Created at 58 minutes ago
Created at 1 hour ago
Created at 2 hours ago
Created at 2 hours ago
started
Created at 3 hours ago
Created at 3 hours ago
Created at 3 hours ago
issue comment
ui bloked when drawToBitmap()

yes , i want to make video from lottie in that making each frame and convert into bitmap .in this method i used mediamuxer for making video and my code is

val max = lottieAnimationView.maxFrame.toInt() CoroutineScope(Dispatchers.Default).launch { for (i in 0 until max) { try { lottieAnimationView.frame = i var bitmap = lottieAnimationView.drawToBitmap() frameBuilder.createFrame(bitmap , i) } catch (e: Exception) { e.printStackTrace() } }}

Only the original thread that created a view hierarchy can touch its views. in that line lottieAnimationView.frame = i and set outside of CoroutineScope then not generate proper video every time set last frame so video is not perfect frame by frame .and apply this all is main thread then all worked but ui is block. how to solve this ?

Created at 4 hours ago
started
Created at 4 hours ago
Created at 4 hours ago
issue comment
ERR_REQUIRE_ESM in Next.js app

Thanks for the great thoughts, Jordan 🙏 I agree going ESM-only would be the least ideal. Here are my thoughts on the other options

  1. Since d3-* are so fundamental to @visx/* I don't think this is feasible unfortunately
  2. d3 made the ESM-only decision quite a while ago and there have since been several security fixes I don't think they'll backwards-patch (the entire reason we upgraded to these ESM-only packages and released a major version bump was to fix a security vulnerability). One possible option we could consider here is using victory-vendor/d3-* packages. They faced a similar dllemma and decided to transpile & release their own CJS version of d3-* packages. This could be viable, my only concern is possible TS clashes and this wouldn't work for any future lib we depend on that went ESM-only
  3. I think this solution would be the simplest solution if it works, so is worth trying / would be the first thing I would try from here. I would note that we use next.js for our demo site, so we could test the feasibility ourselves with this.
  4. again, hoping that we can avoid this.

I am very limited on bandwidth the next couple of weeks, so if anyone would like to explore #3 I'd be happy to review/collaborate on a branch.

Created at 5 hours ago
Created at 5 hours ago
Created at 5 hours ago
Created at 5 hours ago
Created at 5 hours ago
Created at 6 hours ago
started
Created at 7 hours ago
started
Created at 7 hours ago
Created at 8 hours ago
Created at 8 hours ago
Created at 8 hours ago
Created at 10 hours ago
started
Created at 10 hours ago
Created at 11 hours ago