Node.js Translation to Spanish - (1092 words) (Part 50)

alt

Repository

Project Details

Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside of a browser.

Node.js came into existence when the original developers of JavaScript extended it from something you could only run in the browser to something you could run on your machine as a standalone application.

In simple words, it's an open source execution environment for developing web applications, which is event-based, it uses the V8 engine to provide an execution environment that compiles and executes JavaScript at a higher speed. It is possible to run Node.js without any restriction on Windows, Linux and Mac OS X.

It should be noted that it is NOT a server language, this means that it executes code, so it could be understood as an interpreter.

Contribution Specifications

Node.js is currently being translated into 33 languages. I'm contributing to translate it into the Spanish language.

So far, we have managed to translate 50% of the project!

Translation Overview

I continue with the ChangeLog_V7.md folder

In my previous contributions, I explained what a changelog is about. A Changelog is a record of all the notable changes made to a project, it usually includes change records such as new features or bug fixes. It includes all the changes historically, although it is intended that a Changelog does not include all the changes, but rather it contains a list of notable changes ordered chronologically for each version of a project.

During this contribution, I finished translating the commits belonging to the version 7.2.1, 7.2.0, and I started with the version 7.1.0

Examples:

English:

803f6b3091 - doc: fix linting command for vcbuild (Rich Trott) #11151

Spanish:

803f6b3091 - doc: corregir comando de linting para vcbuild (Rich Trott) #11151

Linting is the process of running a program that will scan the code for possible errors.

via Giphy.

Originally, lint was the name of a programming tool used to detect suspicious, confusing or incompatible code; that is, programming errors that escape the usual syntactic analysis done by the compiler.

In this commit it happens that currently, vcbuild only supportsjslint. vcbuild lint will not work because there is nolint task specified in vcbuild.bat; so it is indicated to update the documentation to be able to use vcbuild jslint instead.

English:

64854f625b - tools: add ESLint rule for assert.throws arguments (Michaël Zasso) #10089

Spanish:

64854f625b - tools: añadir regla de ESLint para los argumentos de assert.throws (Michaël Zasso) #10089

Now that we know what a linter does, we can take this commit as an example to talk about ESLint, a linting tool for Javascript.

alt

via ESLint

The purpose of ESLint is to find these errors without having to execute the code and be able to correct them manually, or even some errors can be corrected automatically. This is a brief demonstration of ESLint's work:

68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f3133353937372f323335313230362f38306536366364322d613537392d313165332d396338302d6538336565646637356164632e676966.gif

via Atom

There are some other linters for JavaScript, however ESLint has become very popular in the community because it is based on rules that are 100% configurable.

It's required to add an ESLint rule in this commit because the second argument to "assert.throws" is usually a function for the thrown error. However, the function also accepts a string and in this case it is interpreted as a message for the AssertionError and not used for validation and it's common for people to forget this and pass to validation string by mistake.

This new rule verifies that a string literal will never be passed as a second argument to "assert.throws".