main-thread-scheduling
Fast and consistently responsive apps using a single function call (by astoilkov)
feedback
Public feedback discussions for npm (by npm)
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
| main-thread-scheduling | feedback | |
|---|---|---|
| 8 | 10 | |
| 1,186 | 137 | |
| - | - | |
| 8.9 | 1.8 | |
| 30 days ago | 6 months ago | |
| TypeScript | ||
| MIT License | Creative Commons Attribution 4.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
main-thread-scheduling
Posts with mentions or reviews of main-thread-scheduling.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-04.
-
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.
feedback
Posts with mentions or reviews of feedback.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-04.
-
'everything' blocks devs from removing their own NPM packages
no-one-left-behind[1] was not even a year ago, and yet the link on npm[2] explaining why it was removed is already broken. Classic JS ecosystem.
1: https://github.com/npm/feedback/discussions/858
2: https://www.npmjs.com/package/no-one-left-behind
- Termux and nvm
-
Better npm search proposal
I created a new discussion in the npm/feedback repo to share my idea. I also mentioned my idea in relevant discussions: npm scores, Weird search behavior with stats, and Improve search functionality on npmjs.com.
-
Badge on NPM packages to show support for ES modules
We encourage you to open a discussion if you have suggestions for how we can improve npm. You don't need to have a solution to the problem you are facing to kick off a discussion. We are hoping to foster productive and collaborative conversations, so please check out how to give good feedback if you want some guidance on how to kick off a successful discussion.
-
Popular 'coa' NPM library hijacked to steal user passwords
There is an ongoing discussion about 2FA and possible bandaids for this sort of problem in the npm community forum: https://github.com/npm/feedback/discussions/588
- [Question] Response timeouts for packages with package-lock file
-
Dependency issues/warnings with setting up Gatsby + Tailwind
See - https://github.com/npm/feedback/discussions/191
-
Choosing the right runtime matters
Now there have been some discussions around to mitigate these things which might have gone side ways like https://npm.community/t/blacklist-entire-packages/9659/4 and https://github.com/npm/feedback/discussions/272. Of course there might be tools which you can use, such as running a commercial npm registry in proxy mode with blacklisting support. But what are the basic features you have as a developer that can be use to mitigate these things ?
-
Cannot Add Angular Material, can you tell me what this means?
This is likely the issue as npm 7 auto installs peer dependencies, which will fail on conflicting dependents.