[Translation][Spanish] Node.js (1052 words) (Part 48)

node.png

Repository

https://github.com/nodejs/i18n

Project Details

Node.js, by definition, is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside the browser. This means that now it is possible to execute a program written in JS outside a web browser such as Google Chrome, Safari, etc. This creates an extension to what the language can do, besides just creating interactive websites. With the help of the V8 JavaScript runtime engine, it can now take the code and convert it into a faster machine code, e. g., Node.js eliminates the waiting and continues to take care of the next task.

From my personal perspective, Node.js represents an advantage for the coders to write code, since it still has all the capabilities and functionalities JavaScript offers, but now in a more extended way. Also, thanks to all the time I have been contributing with this project, I have realized the huge amount of time and effort that the Node.js team has taken in order to make it as good as it is and also to improve it with every single upgrade.

You can take a look at their Crowdin project here.

Contribution Specifications

  • Translation Overview

This is the 48th translation I made for the Node.js project, and on this contribution I continued translating the PULL-REQUESTS.MD folder. Such folder I define it as follows:

-- PULL-REQUESTS.MD: This folder's intention is to show the collaborators how to exactly create a pull request. It shows all the steps one has to follow in order to do so and also the steps taken for that request to be either accepted or denied. The whole tutorial is made out of 10 steps, and after that it advises how to properly review every single detail of the PR.

On this contribution there were not found any complex terms that needed further information in order to be translated properly. However, I found a term that I had not knowledge of and I would like to share it with you.

The term is Lint. It refers to a process or a tool that analyzes sorce code by running a program to flag programming errors, bugs, stylistic errors and suspicious constructs. It is also known as linter, and the term was the name originally given to a particular software that could flag some suspicious and non-portable constructs (mostly bugs) in C language source code. Currently the term is applied generically to any tool, program or software that can do so in software written in any computer language.

Now, why is it important or what makes the linter useful? Well, it does not only help you to detect errors (or things that may look like), but it also helps you to avoid them.

A linter will help you catch bugs in a few scenarios. Let's take a look at some examples:
Screen Shot 20190220 at 3.02.07 PM.png

With the JavaScript Style Guide, a set of rules based on the eslint, the linter would throw us two errors. The first one is that runnable is never used, and the second one on line #3 is using an undeclared variable. Obviously there is just one error, the type error on line #3, but the linter would tell you both.

Detecting these errors while we write the code and not when we execute the app will save a lot of time,  that could be a huge amount of time if the app is running in production. We could literally spend hours debugging in the worst case, but with a linter we get immediate feedback.

There are plenty of ways to use a linter. Let's look at some of them:

-- Using a plugin in your text editor: to get immediate feedback, just add a linter plugin to your text editor.

-- Create an NPM script: add your linter as a dev dependency in your package.json.

-- Git hook: use lint-staged with husky or pre-commit, or just have a small script that is invoked on a standard git pre-commit.

Examples of strings translated:

1. EN: Approval and Request Changes Workflow

SP: Flujo de Trabajo de Aprobación y Solicitud de Cambios

2. EN: If you happen to make a mistake in any of your commits, do not worry.

SP: Si comete un error en cualquiera de sus commits, no se preocupe.

3. EN: GitHub will automatically update the Pull Request.

SP: GitHub actualizará automáticamente la Pull Request.

References:

-- Daily JS. Why you should always use a Linter? (https://medium.com/dailyjs/why-you-should-always-use-a-linter-and-or-pretty-formatter-bb5471115a76)

-- Wikipedia. Lint (https://en.wikipedia.org/wiki/Lint_(software))

-- Stack Overflow. Lint (https://stackoverflow.com/questions/8503559/what-is-linting)

  • Languages

I translated from English to Spanish.

I have translated over 100,000 words utilizing the Crowdin platform and this has given me experience to always grant great quality translations.

  • Word Count

I have translated 1,052 words. This contribution has been made between the dates Feb/16/2019 and Feb/19/2019, when I realized the translation, and Feb/20/2019, when I realized the corrections.

Previous translations on this project:

Proof of Authorship

My Crowdin profile
Qma5ZvDxgbK8cpmMkPenWW8sXpc7UDNsT2hNBiGQHtRNwh.png

Word Count

Screen Shot 20190220 at 3.16.03 PM.png

Sort:  

Greetings, @samuellmiller. Thanks for submitting your contribution!

  • The presentation and contents of your post are fulfill the requirements for a complete evaluation of your contribution.
  • The translated content fits coherently the general meaning and use of the enlisted strings.
  • You an important concept you learnt while you were doing this translation.
  • Your writing style and the use you did of the terminology involved in this translation were precise and adequate.
  • You also added examples of your translation job on the addressed folder... Great!

Congratulations on this contribution!

Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.

To view those questions and the relevant answers related to your post, click here.


Chat with us on Discord

Thank you for your review, @alejohannes! Keep up the good work!

Congratulations @samuellmiller! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

You received more than 5000 upvotes. Your next target is to reach 6000 upvotes.

Click here to view your Board
If you no longer want to receive notifications, reply to this comment with the word STOP

Support SteemitBoard's project! Vote for its witness and get one more award!

Hi @samuellmiller!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server

Hey, @samuellmiller!

Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!

Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).

Want to chat? Join us on Discord https://discord.gg/h52nFrV.

Vote for Utopian Witness!