Node.js Translation to Spanish - (1352 words) (Part-65)

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.

Captura de pantalla 20190518 a las 08.16.04.png

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

Translation Overview

I started the translation of the folder N-api.md.

N-API (pronounced N as in the letter, followed by API) is an API for building native Addons. It is independent from the underlying JavaScript runtime (ex V8) and is maintained as part of Node.js itself.

Previously, I briefly explained what an API is. If you want to see more information about it, you can visit this post.

The N-API is an API that ensures ABI stability across Node.js versions and different compiler levels. And an ABI (application binary interface) it's the interface between two program modules, it determines details such as how to call functions, in which binary format information should be passed from one program component to the next, or to the operating system in the case of a system call.

In this part of the module, how to work with JavaScript properties is explained.

N-API exposes a set of APIs to create all types of JavaScript values. Fundamentally, these APIs are used to do one of the following:

Create a new JavaScript object
Convert from a primitive C type to an N-API value
Convert from N-API value to a primitive C type
Get global instances including undefined and null

As an example of the work done, I will use part of this section called Functions to convert from C types to N-API

English:

Functions to convert from C types to N-API

napi_create_int64

This API is used to convert from the C int64_t type to the JavaScript Number type.

The JavaScript Number type is described in Section 6.1.6 of the ECMAScript Language Specification. Note the complete range of int64_t cannot be represented with full precision in JavaScript. Integer values outside the range of Number.MIN_SAFE_INTEGER -(2^53 - 1) - Number.MAX_SAFE_INTEGER (2^53 - 1) will lose precision.

napi_get_arraybuffer_info

This API is used to retrieve the underlying data buffer of an ArrayBuffer and its length.

WARNING: Use caution while using this API. The lifetime of the underlying data buffer is managed by the ArrayBuffer even after it's returned. A possible safe way to use this API is in conjunction with [napi_create_reference][], which can be used to guarantee control over the lifetime of the ArrayBuffer. It's also safe to use the returned data buffer within the same callback as long as there are no calls to other APIs that might trigger a GC.

Spanish:

Funciones para convertir de tipos de C a N-API

napi_create_int64

Esta API se utiliza para convertir desde el tipo de C int64_t al tipo de Número de JavaScript.

El tipo de Número de JavaScript se describe en la Sección 6.1 de las Especificaciones del Lenguaje ECMAScripts. Tenga en cuenta que el rango completo de int64_t no puede ser representado con total precisión en JavaScript. Los valores enteros fuera del rango de Number.MIN_SAFE_INTEGER -(2^53 - 1) - Number.MAX_SAFE_INTEGER (2^53 - 1) perderán precisión.

napi_get_arraybuffer_info

Esta API se utiliza para recuperar el buffer de datos subyacente de un ArrayBuffer y su longitud.

ADVERTENCIA: Tenga cuidado al utilizar esta API. El ArrayBuffer administra la vida útil del buffer de datos subyacente incluso después de su devolución. Una manera segura y posible de utilizar esta API es hacerlo en conjunto con [napi_create_reference][], la cual puede ser utilizada para garantizar el control sobre la vida útil del ArrayBuffer. También es seguro utilizar el buffer de datos devuelto dentro de la misma callback de terminación, siempre que no existan llamadas a otras APIs que puedan desencadenar un GC.