bases VS Bee-Queue

We will install ready-to-use Typescript base configurations instead of starting from scratch. In this article, we will use Typescript base configurations for node version 20. If you are using a different version of node, visit the tsconfig bases docs to find out what you need. You can also create a Typescript configuration file with settings that work for you.

This Visual Studio Code extension simplifies the process of selecting and applying TypeScript configuration files (`tsconfig.json`) from the https://github.com/tsconfig/bases repository. With this extension, you can effortlessly browse through available configuration

Steal from this repo: https://github.com/tsconfig/bases/blob/main/bases/next.json

I personally am a big advocate for writing the least amount of tsconfig possible, and the tsconfig/bases package serves as a great source for getting tsconfig templates.

Possibly depends on your tsconfig. We use the recommended base configs from here https://github.com/tsconfig/bases

A tsconfig.json preset that ensures type safety;

The same configuration is also available for other nodejs versions like 14 and 12.

After installing, we also need to set up a basic tsconfig.json file for how we want tsc to behave with our app. We will use one of the recommended tsconfig files here: https://github.com/tsconfig/bases#centralized-recommendations-for-tsconfig-bases. This contains a list of community recommended configs depending on your app type. We’re using Node 16 and want to be extremely strict on the first pass to clean up any bad code habits and enforce some consistency. We’ll use the one located: https://github.com/tsconfig/bases/blob/main/bases/node16-strictest.combined.json.

You'll need @typescript-eslint/parser to get it working with eslint, then I would add @typescript-eslint/recommended as a plugin, then add prettier-eslint for formatting. What's more important is having a really good tsconfig file, I would recommend extending something from https://github.com/tsconfig/bases

The above configuration file extends the base configuration provided by the TypeScript team for Node.js v16. Additional options or overrides may be included through the compilerOptions property. It also specifies that all the files in the src directory should be included in the program, but everything in the node_modules directory is skipped entirely. Both the include and exclude properties support glob patterns.

You could use a Redis based job system like https://github.com/bee-queue/bee-queue for maintenance and email. The jobs could be populated by the API service, some cron scripts, and whatever else, while you'd have dedicated worker processes (written in Node.js?) pulling the jobs and running them.

The Node.js libraries BullMQ and Bee Queue are also infrastructure and interface. However, you typically have to use their interface.

I'm a fan of bee-queue for this when working in Node, but it's just a wrapper around reliable queue patterns in Redis; you might want to investigate how it works (the readme is quite good) for your own use case, or find an equivalent for your environment. The key is it's designed for short tasks (seconds long, not minutes or hours), and you can receive a result back from the task unlike some fire-and-forget queueing solutions.

I'd also consider something like bee-queue, which would enable you to scale across processes or even across multiple server machines.

For NodeJS, there are BullMQ(successor of Bull), Bull and Bee Queue

bee-queue for offloading tasks onto non-web-server machines