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.
8/28/2019
Node.js v12.9.1 Documentation
https://nodejs.org/api/all.html
1/807
Welcome to the official API reference documentation for Node.js!
Node.js is a JavaScript runtime built on the V8 JavaScript engine .
Report errors in this documentation in the issue tracker . See the contributing guide for directions on how to submit pull requests.
Throughout the documentation are indications of a section's stability. Some APIs 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.
The stability indices are as follows:
Stability: 0 - Deprecated. The feature may emit warnings. Backward compatibility is not guaranteed.
Stability: 1 - Experimental. The feature is not subject to Semantic Versioning rules. Non-backward compatible changes or removal may
occur in any future release. Use of the feature is not recommended in production environments.
Stability: 2 - Stable. Compatibility with the npm ecosystem is a high priority.
Use caution when making use of Experimental features, particularly within modules. End users may not be aware that experimental features
are being used. Bugs or behavior changes may surprise end users when Experimental API modifications occur. To avoid surprises, use of an
Experimental feature may need a command-line flag. Experimental features may also emit a warning .
Every .html document has a corresponding .json document. This is for IDEs and other utilities that consume the documentation.
Node.js functions which wrap a system call will document that. The docs link to the corresponding man pages which describe how the system
call works.
Most Unix system calls have Windows analogues. Still, behavior differences may be unavoidable.
Node.js v12.9.1 Documentation
About this Documentation
Contributing
Stability Index
JSON Output
System calls and man pages
Usage & Example
Usage
8/28/2019
Node.js v12.9.1 Documentation
https://nodejs.org/api/all.html
2/807
node [options] [V8 options] [script.js | -e "script" | - ] [arg