npm-search
main-thread-scheduling
npm-search | main-thread-scheduling | |
---|---|---|
1 | 8 | |
128 | 1,156 | |
0.8% | - | |
6.6 | 8.9 | |
4 days ago | 20 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
npm-search
-
Better npm search proposal
I contacted Algolia and they gave me access to their npm index. I can use it for a basic implementation of my idea because it includes the history of all the releases. Also, the API returns sorted search results that can be used as a fallback or a base score. Not sure if this will be enough to produce consistently better results compared to other search engines.
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?
client-side-databases - An implementation of the exact same app in Firestore, AWS Datastore, PouchDB, RxDB and WatermelonDB
promise-workers
algoliasearch-netlify - Official Algolia Plugin for Netlify. Index your website to Algolia when deploying your project to Netlify with the Algolia Crawler
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
docsearch - :blue_book: The easiest way to add search to your documentation.
worktank - A simple isomorphic library for executing functions inside WebWorkers or Node Threads pools.
feedback - Public feedback discussions for npm
talk - Issues and discussions for the notes app, Nota.
ticker-symbol-search - Seamlessly integrate a search engine to find live ticker symbols into your web app
Fuse - Lightweight fuzzy-search, in JavaScript
autocomplete - đź”® Fast and full-featured autocomplete library
searchkit - Search UI for Elasticsearch & Opensearch. Compatible with Algolia's Instantsearch and Autocomplete components. React & Vue support