Serverless-Boilerplate-Express-TypeScript VS ESLint

You can find more details in my open source boilerplate: https://github.com/ixartz/Serverless-Boilerplate-Express-TypeScript where I'm using TypeScript.

You can check out the GitHub repo for more details at: Node.js Boilerplate with Serverless and Prisma

Here is the link to the Node.js Boilerplate code: https://github.com/ixartz/Serverless-Boilerplate-Express-TypeScript

You can checkout the Serverless Boilerplate Typescript GitHub repo.

As you might know, AWS has recently announced AWS Lambda Function URLs. This is a new feature that allows you to deploy your lambda behind a HTTPS endpoint without API Gateway. So, no need to set up a API gateway with related cost associated to it or add complexity to your serverless architecture for a single lambda function. I'm the author of a Serverless Boilerplate Template that uses Express.js with AWS Lambda. Usually, I got a lot of questions on why I add Express.js to my boilerplate code. Indeed, adding Express.js with API Gateway is redundant and it's not necessary. It'll increase the deployed package size. Now with Lambda Function URLs, you don't need an API Gateway all the time. Without API gateway, all HTTP requests are sending to one lambda function. That means you need a Web framework to handle the request like Express.js. To be clear and avoid any confusion, API gateway is still a solution. But, based on your context and your needs, you can choose to use Lambda Function URLs and remove the API gateway. In the past, a lot of people were suggesting me to remove Express.js from my starter code. Now with Lambda Function, I'm not sure if it's a good idea to remove it from your boilerplate code. What is your thoughts on this?

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: