Kutt.it VS ESLint

Tangentially related: I'm in search of a lightweight self-hosted URL shortener. Tried shlink[0] but man it's a bit of a bear, requiring 5 (yes, five) separate Docker containers. Also tried kutt[1] but it appears to be abandoned.

[0] https://github.com/shlinkio/shlink

[1] https://github.com/thedevs-network/kutt

I then switched to kutt(https://github.com/thedevs-network/kutt), and make a report to Google(Apr 26, 2023).

Az eredeti projekt: https://github.com/thedevs-network/kutt

Kutt: Short links

I run kutt on one of my servers. The developers also host a public instance.

Kutt

here's a short list I made for myself: https://github.com/thedevs-network/kutt install kuma uptime vaultwarden Watchtower (automatically update containers) Portainer (easy to use frontend for container management) domain mapping reverse proxy dashmachine lets encrypt

After some research, I decided to give Kutt a try. It's open source and free, and there is a node SDK which can make it easy to use.

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.

eslint is used to avoid code errors

No lint errors: The committed code does not contain any lint errors (eslint).

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

GitHub | Website

ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript.

ESLint

1. Lack of Static Code Analysis Static code analysis tools like TypeScript and ESLint play a crucial role in identifying and preventing bugs. TypeScript provides static typing, enhancing the robustness of the code. ESLint detects issues and enforces coding standards. The absence of these tools can significantly elevate the likelihood of bugs due to the lack of early detection and guidance provided during development.

The industry standard for JavaScript is ESLint. VS Code has an ESLint extension. Here is a guide.

All modern linters incorporate functionality for extending configurations, although the syntax for this is often implemented differently. Taking ESLint as an example, in its latest versions, the primary extension method is through the use of the spread operator. Let's take a look at an example: