Node.js Translation to Spanish - (1225 words) (Part 30)

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 31% of the project.

Translation Overview

I continue with my contribution in the ChangeLog_V8.md folder.

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.

For large projects, there are many people who work in systems with different ideas about design and different knowledge about standards. This leads to a totally different technique, and the more documented it is, the more people can work together.

I finished translating the corresponding commits to version 8.3.0, I translated all of the version 8.2.1 (it should be noted that there were only three) and now we are going with the commits of version 8.2.0.

Let's see this commit of version 8.3.0:

English:

58446912a6 - net: fix bytesWritten during writev (Brendan Ashworth) #14236

Spanish:

58446912a6 - net: corregir bytesWritten durante writev (Brendan Ashworth) #14236

When a writev is caused on a socket, previously net would call Buffer.byteLength on the array of buffers and chunks. This throws a TypeError, because Buffer.byteLength throws when passed a non-string.

In the commit dbfe8c4, the behavior was changed to throw when passed a non-string. This is the correct behavior. Previously, it would cast the argument to a string, so before this commit, bytesWritten would give an erroneous value. This commit corrects the behavior equally both before and after dbfe8c4.

This commit fixes this bug by iterating over each chunk in the pending stack and calculating the length individually. Also adds a regression test. This additionally changes an instanceof Buffer check to typeof !== 'string', which should be equivalent.

These were the notable changes from version 8.2.1:

The writes are no longer aborted if the socket is missing.
triggerAsyncId can now be undefined.
Streams no longer attempt to process data when they are destroyed.

And, of course, here is a commit of version 8.2.0:

English:

dfc46e262a - (SEMVER-MINOR) cluster: overriding inspector port (cornholio) #14140

Spanish:

dfc46e262a - (SEMVER-MINOR) cluster: anulación del puerto del inspector (cornholio) #14140

Added an option to override the inspector port for workers using settings.inspectPort and will override the default port increment behavior.

Previously, cluster workers were restricted to incrementing from the master's debug port. But now, the use of this option even allows configuring port 0 for the entire cluster.

Languages

This contribution was translated from English to Spanish.

Word Count

In this contribution, I've translated 1225 words
I've translated a total of 35230 words so far.

Previous translations on this project

Proof of Authorship

You can check My Crowdin Profile for verify my contribution in this project.