Repository

https://github.com/nodejs/i18n

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 34% 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've finished translating the commits of version 8.1.1, the commits of version 8.1.0, and started version 8.0.0.

I explained a bit about version 8.1.1 in my previous contribution and I included some examples of the translated commits.

About version 8.1.0, these were its changes:

-When one Promise leads to the creation of a new Promise, the parent Promise will be identified as the trigger

async_hooks init callback will be activated when the promise is newly created. In the previous version, the main promise that is passed from Chrome V8 PromiseHook is ignored, so it can't be said that the promise is totally new or a promise chained.

• libuv has been updated to 1.12.0

• npm has been updated to 5.0.3

• The fs.exists() function now works correctly with util.promisify()

• fs.Stats times are now also available as numbers

• It is now possible to bind to a random port using --inspect=0. This was done through the commit cc6ec2fb27

• A regression in the Zlib module that made it impossible to properly subclasses zlib.Deflate and other Zlib classes has been fixed.

Some commits of this version:

English:

25a05e5db1 - test: fix flaky test-fs-watchfile on macOS (Rich Trott) #13252

Spanish:

25a05e5db1 - test: corregir test-fs-watchfile defectuosa en macOS (Rich Trott) #13252

On macOS, a watcher created with fs.watch() does not necessarily start receiving events immediately. So it can miss a change by fs.writefile() if it comes very soon after the watcher is created. It's required to repair the flakyness of the test caused by this using setInterval () to repeat the write action.

---

English:

376ac5fc3e - inspector: Allows reentry when paused (Eugene Ostroukhov) #13350

Spanish.

376ac5fc3e - inspector: Permitir el reingreso cuando está en pausa (Eugene Ostroukhov) #13350

This change allows reentering the message dispatch loop when the Node is paused. This is necessary when the pause happened as a result of the message sent by a debug frontend, such as evaluating a function with a breakpoint inside.

---

Now, regarding the version 8.0.0, Node.js 8.0.0 is a major new release that includes a significant number of semver-major and semver-minor changes, but MANY changes. Here I will list the most outstanding:

• The async_hooks module has landed in core.

• Using the --pending-deprecation flag will cause Node.js to emit a deprecation warning when using new Buffer(num) or Buffer(num).

• new Buffer(num) and Buffer(num) will zero-fill new Buffer instances

• Many Buffer methods now accept Uint8Array as input

• Argument and kill signal validations have been improved

• Child Process methods accept Uint8Array as input

• Error events emitted when using console methods are now supressed.

• The npm client has been updated to 5.0.0

• V8 has been updated to 5.8 with forward ABI stability to 6.0

• Native Promise instances are now Domain aware.

• It has begun to assign static error codes to errors generated by Node.js. This has been done through multiple commits and is still a work in progress.

• The utility class fs.SyncWriteStream has been deprecated

• The deprecated fs.read() string interface has been removed

• Improved support for userland implemented Agents

• Outgoing Cookie headers are concatenated into a single string

• The httpResponse.writeHeader() method has been deprecated

• New methods for accessing HTTP headers have been added to OutgoingMessage

• All deprecation messages have been assigned static identifiers

• The legacy linkedlist module has been removed

• Experimental support for the new N-API API has been added

• Process warning output can be redirected to a file using the --redirect-warnings command-line argument

• Process warnings may now include additional detail

• REPL magic mode has been deprecated

• NODE_MODULE_VERSION has been updated to 57

• Add --pending-deprecation command-line argument and NODE_PENDING_DEPRECATION environment variable

• The --debug command-line argument has been deprecated. Note that using --debug will enable the new Inspector-based debug protocol as the legacy Debugger protocol previously used by - Node.js has been removed.

• Stream now supports destroy() and _destroy() APIs

• Stream now supports the _final() API

• The rejectUnauthorized option now defaults to true

• The tls.createSecurePair() API now emits a runtime deprecation

• A runtime deprecation will now be emitted when dhparam is less than 2048 bits

• The WHATWG URL implementation is now a fully-supported Node.js API

• Symbol keys are now displayed by default when using util.inspect()

• toJSON errors will be thrown when formatting %j

• Convert inspect.styles and inspect.colors to prototype-less objects

• The new util.promisify() API has been added

• Support Uint8Array in Zlib convenience methods

• Zlib errors now use RangeError and TypeError consistently

Some commits:

English:

beca3244e2 - (SEMVER-MAJOR) buffer: allow Uint8Array input to methods (Anna Henningsen) #10236

Spanish:

beca3244e2 - (SEMVER-MAJOR) buffer: permitir la entrada de Uint8Array a los métodos (Anna Henningsen) #10236

In this commit, it's requested to allow all methods in buffer andBuffer to take Uint8Array Arguments where it makes sense. On the native side, there is effectively no difference, and as a bonus the isUint8Array check is faster thaninstanceof Buffer.

---

English:

[9a0829d728]https://github.com/nodejs/node/commit/9a0829d728 - (SEMVER-MAJOR) buffer: stricter argument checking in toString (Nikolai Vavilov) #11120

Spanish:

[9a0829d728]https://github.com/nodejs/node/commit/9a0829d728 - (SEMVER-MAJOR) buffer: comprobación de argumentos más estricta en toString (Nikolai Vavilov) #11120

This prevents the confusing behavior of buf.toString(0, 5) by disallowing passing 0 as the encoding.

Languages

This contribution was translated from English to Spanish.

Word Count

• In this contribution, I've translated 1294 words
• I've translated a total of 40435 words so far.

Previous translations on this project

• Part 33
• Part 32
• Part 31
• Part 30
• Part 29
• Part 28
• Part 27
• Part 26
• Part 25
• Part 24
• Part 23
• Part 22
• Part 21
• Part 20
• Part 19
• Part 18
• Part 17
• Part 16
• Part 15
• Part 14
• Part 13
• Part 12
• Part 11
• Part 10
• Part 9
• Part 8
• Part 7
• Part 6
• Part 5
• Part 4
• Part 3
• Part 2
• Part 1

Proof of Authorship

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