Node.js v0.10.35 API详解与模块教程

5星 · 超过95%的资源需积分: 0 159 浏览量更新于2024-07-22 1 收藏 1.92MB PDF 举报

Node.js v0.10.35 官方文档详细介绍了Node.js版本0.10.35的API及其使用方法。本篇文档涵盖了广泛的Node.js核心概念和技术细节，包括： 1. **稳定性指数**：文档强调了该版本的稳定性，意味着它可能已经经过了充分的测试和优化，但开发者仍需了解潜在的不稳定因素和未来可能的更改。 2. **JSON 输出**：Node.js 0.10.35 提供了对JSON数据的处理功能，这对于与前后端交互、数据交换以及构建Web应用至关重要。 3. **全局对象**： - **global**：全局作用域，允许访问所有模块和函数。 - **process**：提供了与操作系统交互的接口，如进程ID、环境变量等。 - **console**：控制台输出工具，可用于调试和日志记录，包括log、info、error、warn、dir、time、timeEnd、trace和assert方法。 4. **Buffer 类**：用于在内存中操作二进制数据，是Node.js中处理非文本数据的基础。 5. **require()函数**：核心模块加载机制，用于引入其他模块并执行其代码。`require.resolve()`用于查找模块路径，`require.cache`存储已加载模块，`require.extensions`定义扩展名与模块关联的方式。 6. **特殊变量**： - `__filename`：当前模块的文件路径。 - `__dirname`：当前模块所在的目录路径。 - `module`：提供有关模块自身的信息。 - `exports`：导出模块的接口，供其他模块引用。 7. **定时器和回调函数**： - `setTimeout`和`clearTimeout`用于延迟执行回调函数。 - `setInterval`和`clearInterval`用于周期性执行任务。 - `unref`和`ref`控制定时器是否阻塞事件循环。 - `setImmediate`和`clearImmediate`处理异步队列中的回调。 8. **模块管理**： - **模块循环**：避免无限递归加载模块时可能出现的问题。 - **核心模块**：Node.js自带的一组基础模块。 - **文件模块**：通过相对或绝对路径加载的自定义模块。 - **`node_modules`目录**：存放第三方模块的组织结构。 - **模块缓存**：为了提高性能而存储已加载模块的机制。通过阅读这份文档，开发者可以深入理解如何在Node.js环境中编写高效、可维护的代码，并掌握核心组件的工作原理。学习完这些内容后，可以熟练地利用Node.js进行Web服务器开发、网络编程、数据处理等各种应用场景。

15/1/6 09:16Node.js v0.10.35 Manual & Documentation

第 16 （共 198 ）ﬁle:///Users/lvyue/Documents/api/Nodejs10.35%20API.html#all_require

process#

{Object}

The process object. See the process object section.

console#

{Object}

Used to print to stdout and stderr. See the console section.

Class: Buffer#

{Function}

Used to handle binary data. See the buffer section

require()#

{Function}

To require modules. See the Modules section. require isn't actually a global but rather local to each module.

require.resolve()#

Use the internal require() machinery to look up the location of a module, but rather than loading the module, just return the resolved ﬁlename.

require.cache#

Object

Modules are cached in this object when they are required. By deleting a key value from this object, the next require will reload the module.

require.extensions#

Stability: 0 - Deprecated

Object

Instruct require on how to handle certain ﬁle extensions.

Process ﬁles with the extension .sjs as .js:

require.extensions['.sjs'] = require.extensions['.js'];

Deprecated In the past, this list has been used to load non-JavaScript modules into Node by compiling them on-demand. However, in practice, there are

much better ways to do this, such as loading modules via some other Node program, or compiling them to JavaScript ahead of time.

Since the Module system is locked, this feature will probably never go away. However, it may have subtle bugs and complexities that are best left

untouched.

__ﬁlename#

{String}

The ﬁlename of the code being executed. This is the resolved absolute path of this code ﬁle. For a main program this is not necessarily the same ﬁlename

used in the command line. The value inside a module is the path to that module ﬁle.

Example: running node example.js from /Users/mjr

15/1/6 09:16Node.js v0.10.35 Manual & Documentation

第 17 （共 198 ）ﬁle:///Users/lvyue/Documents/api/Nodejs10.35%20API.html#all_require

console.log(__filename);

// /Users/mjr/example.js

__filename isn't actually a global but rather local to each module.

__dirname#

{String}

The name of the directory that the currently executing script resides in.

Example: running node example.js from /Users/mjr

console.log(__dirname);

// /Users/mjr

__dirname isn't actually a global but rather local to each module.

module#

{Object}

A reference to the current module. In particular module.exports is used for deﬁning what a module exports and makes available through require().

module isn't actually a global but rather local to each module.

See the module system documentation for more information.

exports#

A reference to the module.exports that is shorter to type. See module system documentation for details on when to use exports and when to use

module.exports.

exports isn't actually a global but rather local to each module.

See the module system documentation for more information.

See the module section for more information.

setTimeout(cb, ms)#

Run callback cb after at least ms milliseconds. The actual delay depends on external factors like OS timer granularity and system load.

The timeout must be in the range of 1-2,147,483,647 inclusive. If the value is outside that range, it's changed to 1 millisecond. Broadly speaking, a timer

cannot span more than 24.8 days.

Returns an opaque value that represents the timer.

clearTimeout(t)#

Stop a timer that was previously created with setTimeout(). The callback will not execute.

setInterval(cb, ms)#

Run callback cb repeatedly every ms milliseconds. Note that the actual interval may vary, depending on external factors like OS timer granularity and

system load. It's never less than ms but it may be longer.

The interval must be in the range of 1-2,147,483,647 inclusive. If the value is outside that range, it's changed to 1 millisecond. Broadly speaking, a timer

cannot span more than 24.8 days.

Returns an opaque value that represents the timer.

15/1/6 09:16Node.js v0.10.35 Manual & Documentation

第 19 （共 198 ）ﬁle:///Users/lvyue/Documents/api/Nodejs10.35%20API.html#all_require

;

}

console.timeEnd('100-elements');

console.trace(message, [...])#

Print to stderr 'Trace :', followed by the formatted message and stack trace to the current position.

console.assert(value, [message], [...])#

Similar to assert.ok(), but the error message is formatted as util.format(message...).

Timers#

Stability: 5 - Locked

All of the timer functions are globals. You do not nee d to require() this module in order to use them.

setTimeout(callback, delay, [arg], [...])#

To schedule execution of a one-time callback after delay milliseconds. Returns a timeoutObject for possible use with clearTimeout(). Optionally

you can also pass arguments to the callback.

It is important to note that your callback will probably not be called in exactly delay milliseconds - Node.js makes no guarantees about the exact timing of

when the callback will ﬁre, nor of the ordering things will ﬁre in. The callback will be called as close as possible to the time speciﬁed.

clearTimeout(timeoutObject)#

Prevents a timeout from triggering.

setInterval(callback, delay, [arg], [...])#

To schedule the repeated execution of callback every delay milliseconds. Returns a intervalObject for possible use with clearInterval().

Optionally you can also pass arguments to the callback.

clearInterval(intervalObject)#

Stops an interval from triggering.

unref()#

The opaque value returned by setTimeout and setInterval also has the method timer.unref() which will allow you to create a timer that is active

but if it is the only item left in the event loop won't keep the program running. If the timer is already unrefd calling unref again will have no effect.

In the case of setTimeout when you unref you create a separate timer that will wakeup the event loop, creating too many of these may adversely effect

event loop performance -- use wisely.

ref()#

If you had previously unref()d a timer you can call ref() to explicitly request the timer hold the program open. If the timer is already refd calling ref

again will have no effect.

setImmediate(callback, [arg], [...])#

To schedule the "immediate" execution of callback after I/O events callbacks and before setTimeout and setInterval . Returns an

immediateObject for possible use with clearImmediate(). Optionally you can also pass arguments to the callback.

15/1/6 09:16Node.js v0.10.35 Manual & Documentation

第 20 （共 198 ）ﬁle:///Users/lvyue/Documents/api/Nodejs10.35%20API.html#all_require

Immediates are queued in the order created, and are popped off the queue once per loop iteration. This is different from process.nextTick which will

execute process.maxTickDepth queued callbacks per iteration. setImmediate will yield to the event loop after ﬁring a queued callback to make sure I/O

is not being starved. While order is preserved for execution, other I/O events may ﬁre between any two scheduled immediate callbacks.

clearImmediate(immediateObject)#

Stops an immediate from triggering.

Modules#

Stability: 5 - Locked

Node has a simple module loading system. In Node, ﬁles and modules are in one-to-one correspondence. As an example, foo.js loads the module

circle.js in the same directory.

The contents of foo.js:

var circle = require('./circle.js');

console.log( 'The area of a circle of radius 4 is '

+ circle.area(4));

The contents of circle.js:

var PI = Math.PI;

exports.area = function (r) {

return PI * r * r;

};

exports.circumference = function (r) {

return 2 * PI * r;

};

The module circle.js has exported the functions area() and circumference(). To add functions and objects to the root of your module, you can add

them to the special exports object.

Variables local to the module will be private, as though the module was wrapped in a function. In this example the variable PI is private to circle.js.

If you want the root of your module's export to be a function (such as a constructor) or if you want to export a complete object in one assignment instead of

building it one property at a time, assign it to module.exports instead of exports.

Below, bar.js makes use of the square module, which exports a constructor:

var square = require('./square.js');

var mySquare = square(2);

console.log('The area of my square is ' + mySquare.area());

The square module is deﬁned in square.js:

// assigning to exports will not modify module, must use module.exports

module.exports = function(width) {

return {

area: function() {

return width * width;

剩余197页未读，继续阅读

吕悦ly

粉丝: 0
资源: 4

Node.js v0.10.35 API详解与模块教程

Node.js教程/中文文档/开发指南pdf

how to learn node.js

node.js官方文档下载

Node.js v18.16.0 error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Node Sass does not yet support your current environment: Windows 64-bit wit

npm ERR! gyp ERR! node -v v16.19.1 npm ERR! gyp ERR! node-gyp -v v8.4.1

nodejs中文文档下载

nvm nodejs

最新资源