Node.js Translation to Spanish - 1071 words (Part 28)

This is the 28th Node.js translation report and it is about the 9th version of the change log file. I started this project two months ago with a lot of motivation because contributing in open source projects is a way to make those project's scopes bigger. My way to contribute is translating Node.js into Spanish, and I must say that it is not only me, there is an entire team working on it and this team is supported by Utopian+DaVinci alliance.

Node.js is a huge project, it consists of more than a million words. The Spanish team has been working hard to complete it. I know that the team has a big compromise and will keep the hard work until the end of this excellent project. Let me invite you to keep reading this report, so you can learn more about Node.js

It looks difficult to understand at first, but let me explain it with the next example.

Imagine that you have been developing a new android app that uses the APIs from Google Maps and Twitter. When testing the app, you realize that both APIs are written in different languages and you must change one of them to make it work, but that's a lot of work and goes against the reasons to use an API. Node.js is the solution to problems like this because it allows the union between different programming languages without affecting its performance.

I decided to translate this project because I'm an engineering student and innovation is my passion; I love creating solutions to problems like this. Also, I like sharing information and a way to do it is translating the content of a big project like this so people around the world can access to it and share it too.

I continued with the 9th version of Node.js change log file, but with a specific version, the 9.3.0. This version was porpoised on November 12th of 2017 and has notable changes at hooks, console, deps, module, n-api, process, src, stream and collaborators list; those are different important parts of Node.js that have been improved among the years, as you can see in my previous change log file reports. Some of these changes are simple and other are more complicated, but all of them have the same importance.

During my research of the concepts used in this file, one of them called my attention and it was async-hooks. This term is mentioned a lot of times, which means that is very important, but there is no explanation, so I took a look at Node.js website and found a detailed explanation. The next paragraphs have a summary of what I learned reading about it.

The async_hooks is a module that provides an API to register callbacks tracking the lifetime of asynchronous resources created inside a Node.js application; it means that is a register that allows the program to follow the entire process of these mentioned resources. An asynchronous resource is an object with an associated callback. Tracing asynchronous resources is necessary because they have an unpredictable behavior for the app. I must say that the correct functioning of a Node.js app depends on the order of the functions execution, and with asynchronous objects it is difficult to know when will start another function because the nature of these resources.

As async-hooks is a Node.js module, it has an error handling method. The following explanation is extracted from Node.js official website.

The original language of this change log is English and it was translated into Spanish, which is my native language. I have experience translating in projects like Loopring wallet and Yapbam. These projects make me grow and learn a lot about open source projects.

Some examples of my translation:

You can visit my profile (navx) on Crowdin's website to find proof of authorship. Also, you can visit the Activity tab in the Node.js project and filter my contributions between November 10th and November 11th, which were the dates of the translation and the corrections respectively.