workerize
main-thread-scheduling
| workerize | main-thread-scheduling | |
|---|---|---|
| 1 | 8 | |
| 4,339 | 1,113 | |
| - | - | |
| 0.0 | 8.9 | |
| about 3 years ago | 16 days ago | |
| JavaScript | TypeScript | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
workerize
-
Consistently responsive apps while staying on the main thread
Here are a couple attempts at doing just that.
main-thread-scheduling
-
What is INP and why you should care
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.
-
Main-Thread-Scheduling
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.
-
Better npm search proposal
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.
-
I've made my app's search fast and open-sourced the solution
The library — https://github.com/astoilkov/main-thread-scheduling
- Main thread scheduling — faster apps using a simple API instead of Web Workers
-
Consistently responsive apps while staying on the main thread
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.
What are some alternatives?
partytown - Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
promise-workers
comlink - Comlink makes WebWorkers enjoyable.
dayschedule-widget - Appointment scheduling widget to embed the booking calendar on your website for 1:1, round-robin and group bookings with Google meet, Zoom and MS Teams integrations
threads.js - 🧵 Make web workers & worker threads as simple as a function call.
worktank - A simple isomorphic library for executing functions inside WebWorkers or Node Threads pools.
typed-json-rpc - Simple, statically typed and ergonomic way to do async communications (events, workers, http requests) with json-rpc
talk - Issues and discussions for the notes app, Nota.
workerize-loader - 🏗️ Automatically move a module into a Web Worker (Webpack loader)
npm-search - 🗿 npm ↔️ Algolia replication tool :skier: :snail: :artificial_satellite:
workly - A really simple way to move a function or class to a web worker. 🏋️♀️→ 😄
Fuse - Lightweight fuzzy-search, in JavaScript