Computer programming is the process of designing and building an executable computer program for accomplishing specific computing task. Programming involves tasks such as: analysis, generating algorithms, profiling algorithms' accuracy and resource consumption, and the implementation of algorithms in a chosen programming language (commonly referred to as coding). The source code of a program is written in one or more languages that are intelligible to programmers, rather than machine code, which is directly executed by the central processing unit. The purpose of programming is to find a sequence of instructions that will automate the performance of a task (which can be as complex as an operating system) on a computer, often for solving a given problem. The process of programming thus often requires expertise in several different subjects, including knowledge of the application domain, specialized algorithms, and formal logic.Tasks accompanying and related to programming include: testing, debugging, source code maintenance, implementation of build systems, and management of derived artifacts, such as the machine code of computer programs. These might be considered part of the programming process, but often the term software development is used for this larger process with the term programming, implementation, or coding reserved for the actual writing of code. Software engineering combines engineering techniques with software development practices. Reverse engineering is the opposite process. A hacker is any skilled computer expert that uses their technical knowledge to overcome a problem, but it can also mean a security hacker in common language.
Node.js v10.16.3 Documentation
The goal of this documentation is to comprehensively explain the Node.js API, both from a reference as well as a conceptual point of view. Each
section describes a built-in module or high-level concept.
Where appropriate, property types, method arguments, and the arguments provided to event handlers are detailed in a list underneath the
If errors are found in this documentation, please submit an issue or see the contributing guide for directions on how to submit a patch.
Every file is generated based on the corresponding .md file in the doc/api/ folder in Node.js's source tree. The documentation is generated
using the tools/doc/generate.js program. An HTML template is located at doc/template.html .
Throughout the documentation are indications of a section's stability. The Node.js API is still somewhat changing, and as it matures, certain
parts are more reliable than others. Some are so proven, and so relied upon, that they are unlikely to ever change at all. Others are brand new
and experimental, or known to be hazardous and in the process of being redesigned.
The stability indices are as follows:
Stability: 0 - Deprecated. The feature may emit warnings. Backward compatibility is not guaranteed.
Stability: 1 - Experimental. This feature is still under active development and subject to non-backward compatible changes or removal in
any future version. Use of the feature is not recommended in production environments. Experimental features are not subject to the
Node.js Semantic Versioning model.
Stability: 2 - Stable. Compatibility with the npm ecosystem is a high priority.
Caution must be used when making use of Experimental features, particularly within modules that may be used as dependencies (or
dependencies of dependencies) within a Node.js application. End users may not be aware that experimental features are being used, and
therefore may experience unexpected failures or behavior changes