TypeScript-Handbook
bull
TypeScript-Handbook | bull | |
---|---|---|
6 | 50 | |
4,849 | 15,062 | |
- | 0.5% | |
4.3 | 6.8 | |
almost 4 years ago | 2 days ago | |
JavaScript | JavaScript | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
TypeScript-Handbook
-
An intro to TSConfig for JavaScript Developers
jsx - If you are using JSX (for example with React), this setting determines how your JSX files should be treated(preserve, react, react-native, etc.).
-
Blitz.js – The Missing Fullstack Toolkit for Next.js
Heya! Creator of tRPC here. Seen some comments on trpc's ts perf issues.
Some notes:
- The problems with tRPC "at scale" are fixable by using project references, but not going to downplay that it's an annoying refactor to do (https://github.com/microsoft/TypeScript-Handbook/blob/master...)
-
Please critique my React component. Can it be considered 'clean' React code or no?
By the way, the I-prefix for interfaces is not something you see often in TypeScript. There are several reasons for that though mainly I think it's because the Microsoft TypeScript handbook discouraged it.
-
TypeScript dependent types and function bivariance
The sample code is much older than that. https://github.com/microsoft/TypeScript-Handbook/commit/20ef...
-
Angular end-to-end testing tips
Much cleaner, no CSS selectors in examples but can we improve this even more? Sure! With a common test-specific attribute on every testable element and TypeScript decorators page objects can look a bit fancier:
-
Learnings from migrating Atlaskit to TypeScript
microsoft/TypeScript-Handbook
bull
-
Prioritizing Concurrent Requests: Queuing system to handle distributed processes and messages with NodeJS and Bull
To implement the solution with a queue, I used a package called 'Bull' (https://github.com/OptimalBits/bull). It's a library that helps with distributed job control, providing some very useful solutions for this type of work, such as background job processing, queues with priorities (FIFO, LIFO, and others), among other features. 'Bull' uses Redis for queue storage, so if your application crashes for any reason, once it's back online, it will continue executing the processes that are in the queue. In our case, we'll use the FIFO (First in, first out) queue solution, meaning priority based on arrival order.
-
Instrumentation for Event Driven
We use bull-js for our distributed queue and event-driven library.
-
Redis master/slave setup on Kubernetes throwing error: BRPOPLPUSH { ReplyError: MOVED 2651
I'm using the excellent Redis based Bull.js as a job queue on Kubernetes.
-
How to use Job Queue to handle email sending in your Nestjs server
For Job Queue, NestJs provides a package named @nestjs/bull as an abstraction/wrapper on top of Bull, a popular, well-supported, high-performance Node. js-based Queue system implementation.
-
How do you handle queues in Node.js? Have you ever tried using pgboss?
I'm working on a large ETL project that involves handling queues for file integration. Currently, we are using Redis with Bull (https://www.npmjs.com/package/bull) for this purpose. However, to streamline our architecture and address security concerns, we are considering migrating the queue to PostgreSQL.
-
What is a good background scheduler?
BullMQ is a pretty solid choice: https://github.com/taskforcesh/bullmq It's the successor of Bull: https://github.com/OptimalBits/bull
-
Learning Guidance
For Node specifically, things like Streams, understanding the asynchronous model completely, and the event loop. Also, queues tend to get used a lot in Node, so understanding the basic concepts behind that and how to use something like bull would be useful.
-
image processing in express application, should it be done in a separate thread?
To do this properly, you need to put the task into queue, so if there are 1000 simultaneous uploads it won't kill your server but will be processed one by one. For the queue, see bull. Image hostings like AWS have some functionality for processing on their side, as an option.
- Best development practice for setting up a cron job for each user?
-
How do I implement Heroku background processes?
This is a memory intensive process though and Heroku is OOM'ing with R14 errors. For this they recommend migrating intensive work like this to a Background Job via Redis, implemented in Bull and Throng
What are some alternatives?
Selenium WebDriver - A browser automation framework and ecosystem.
Bee-Queue - A simple, fast, robust job/task queue for Node.js, backed by Redis.
react-redux-typescript-guide - The complete guide to static typing in "React & Redux" apps using TypeScript
kue - Kue is a priority job queue backed by redis, built for node.js.
sink - A cli tool to help with the migration of Atlaskit components from flow to typescript
node-resque - Node.js Background jobs backed by redis.
terraform-aws-ecs-web-app - Terraform module that implements a web app on ECS and supports autoscaling, CI/CD, monitoring, ALB integration, and much more.
agenda - Lightweight job scheduling for Node.js
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
bottleneck - Job scheduler and rate limiter, supports Clustering
better-queue - Better Queue for NodeJS
idoit - Redis-backed task queue engine with advanced task control and eventual consistency