Node.js Translation to Spanish - (1126 words) (Part-61)

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 59% of the project!

Translation Overview

For this contribution, I translated the folder Timers-in-node.md.

The Timers module in Node.js contains functions that execute code after a set period of time.
When we talk about timers, their meaning is not at all different from the concept we already know: it allows us to program the activation or deactivation of different devices in a simple way; in this case, to program functions so that they execute the code when it's required.

Via Giphy

Timers do not need to be imported from a particular function, since all the methods are available globally to emulate the browser JavaScript API.

For example, setTimeout() can be used to schedule code execution after a designated amount of milliseconds. setTimeout() accepts a function to execute as its first argument and the millisecond delay defined as a number as the second argument. Additional arguments may also be included and these will be passed on to the function.

Via Node.js

The above function myFunc() will execute as close to 1500 milliseconds (or 1.5 seconds) as possible due to the call of setTimeout().

As an example of the work done, I will leave a fragment of the execution of the setImmediate() function explained in this module:

English:

setImmediate() will execute code at the end of the current event loop cycle. This code will execute after any I/O operations in the current event loop and before any timers scheduled for the next event loop. This code execution could be thought of as happening "right after this", meaning any code following the setImmediate() function call will execute before the setImmediate() function argument.
The first argument to setImmediate() will be the function to execute. Any subsequent arguments will be passed to the function when it is executed. Here's an example:

The above function passed to setImmediate() will execute after all runnable code has executed, and the console output will be:

setImmediate() returns and Immediate object, which can be used to cancel the scheduled immediate.

Spanish:

setImmediate() ejecutará el código al final del ciclo del bucle de eventos actual. Este código se ejecutará después de cualquier operación de I/O en el bucle de eventos actual y antes de cualquier temporizador programado para el siguiente bucle de eventos. Podría pensarse que esta ejecución de código ocurre "justo después de esto", es decir, cualquier código que siga a la llamada de la función setImmediate() se ejecutará antes del argumento de la función setImmediate().
El primer argumento para setImmediate() será la función a ejecutar. Cualquier argumento posterior se pasará a la función cuando se ejecute. Aquí hay un ejemplo:

La función anterior pasada a setImmediate() se ejecutará después de que se haya ejecutado todo el código ejecutable, y la salida de la consola será: