co VS main-thread-scheduling

Given that the semantics of async functions are quite similar to generator functions, you can use a library the uses the latter to emulate the former – e.g.: https://github.com/tj/co

Then after a while, we resorted to generator functions and cogenerators, which made async code feel like its synchronous, at the cost of wrapping it in a generator function, yielding every line and introducing a cogenerator library (for example co) to deal with unwrapping the promises like the following example, where we could just yield a promise whenever we encounter it and pretend that the yield does not exist on that line of code.

During my research for this post, I discovered main-thread-scheduling, a JavaScript task scheduler developed by Antonio Stoilkov that focuses on helping you improve perceived page performance, and therefore, your INP scores. It uses isInputPending() if available, but provides scheduling functionality for all browsers. Personally, I haven’t had a use case to test this just yet, but at first glance, it’s currently maintained and could be worth a try.

It's done — https://github.com/astoilkov/main-thread-scheduling/commit/0.... Thanks.

A little thing but a great improvement. I'm now wondering why I did that.

Exclude bots. Bots activity should be excluded, otherwise, the search will probably get a lot worse. Also, it opens an opportunity for easy manipulation. For example, a version bump by a bot shouldn't count at all. Similar to how GitHub's repo contributions page work.

The library — https://github.com/astoilkov/main-thread-scheduling

For the past 11 months, I've been working on a very easy-to-use alternative to Web Workers. It's a way to schedule long-running, heavy tasks on the main thread. React has such implementation internally. Browsers are planning to add such functionality in the future.