NineSec Team Shell

# REPL  > Stability: 2 - Stable  The `node:repl` module provides a Read-Eval-Print-Loop (REPL) implementation that is available both as a standalone program or includible in other applications. It can be accessed using: ```js const repl = require('node:repl'); ``` ## Design and features The `node:repl` module exports the [`repl.REPLServer`][] class. While running, instances of [`repl.REPLServer`][] will accept individual lines of user input, evaluate those according to a user-defined evaluation function, then output the result. Input and output may be from `stdin` and `stdout`, respectively, or may be connected to any Node.js [stream][]. Instances of [`repl.REPLServer`][] support automatic completion of inputs, completion preview, simplistic Emacs-style line editing, multi-line inputs, [ZSH][]-like reverse-i-search, [ZSH][]-like substring-based history search, ANSI-styled output, saving and restoring current REPL session state, error recovery, and customizable evaluation functions. Terminals that do not support ANSI styles and Emacs-style line editing automatically fall back to a limited feature set. ### Commands and special keys The following special commands are supported by all REPL instances: * `.break`: When in the process of inputting a multi-line expression, enter the `.break` command (or press <kbd>Ctrl</kbd>+<kbd>C</kbd>) to abort further input or processing of that expression. * `.clear`: Resets the REPL `context` to an empty object and clears any multi-line expression being input. * `.exit`: Close the I/O stream, causing the REPL to exit. * `.help`: Show this list of special commands. * `.save`: Save the current REPL session to a file: `> .save ./file/to/save.js` * `.load`: Load a file into the current REPL session. `> .load ./file/to/load.js` * `.editor`: Enter editor mode (<kbd>Ctrl</kbd>+<kbd>D</kbd> to finish, <kbd>Ctrl</kbd>+<kbd>C</kbd> to cancel). ```console > .editor // Entering editor mode (^D to finish, ^C to cancel) function welcome(name) { return `Hello ${name}!`; } welcome('Node.js User'); // ^D 'Hello Node.js User!' > ``` The following key combinations in the REPL have these special effects: * <kbd>Ctrl</kbd>+<kbd>C</kbd>: When pressed once, has the same effect as the `.break` command. When pressed twice on a blank line, has the same effect as the `.exit` command. * <kbd>Ctrl</kbd>+<kbd>D</kbd>: Has the same effect as the `.exit` command. * <kbd>Tab</kbd>: When pressed on a blank line, displays global and local (scope) variables. When pressed while entering other input, displays relevant autocompletion options. For key bindings related to the reverse-i-search, see [`reverse-i-search`][]. For all other key bindings, see [TTY keybindings][]. ### Default evaluation By default, all instances of [`repl.REPLServer`][] use an evaluation function that evaluates JavaScript expressions and provides access to Node.js built-in modules. This default behavior can be overridden by passing in an alternative evaluation function when the [`repl.REPLServer`][] instance is created. #### JavaScript expressions The default evaluator supports direct evaluation of JavaScript expressions: ```console > 1 + 1 2 > const m = 2 undefined > m + 1 3 ``` Unless otherwise scoped within blocks or functions, variables declared either implicitly or using the `const`, `let`, or `var` keywords are declared at the global scope. #### Global and local scope The default evaluator provides access to any variables that exist in the global scope. It is possible to expose a variable to the REPL explicitly by assigning it to the `context` object associated with each `REPLServer`: ```js const repl = require('node:repl'); const msg = 'message'; repl.start('> ').context.m = msg; ``` Properties in the `context` object appear as local within the REPL: ```console $ node repl_test.js > m 'message' ``` Context properties are not read-only by default. To specify read-only globals, context properties must be defined using `Object.defineProperty()`: ```js const repl = require('node:repl'); const msg = 'message'; const r = repl.start('> '); Object.defineProperty(r.context, 'm', { configurable: false, enumerable: true, value: msg }); ``` #### Accessing core Node.js modules The default evaluator will automatically load Node.js core modules into the REPL environment when used. For instance, unless otherwise declared as a global or scoped variable, the input `fs` will be evaluated on-demand as `global.fs = require('node:fs')`. ```console > fs.createReadStream('./some/file'); ``` #### Global uncaught exceptions  The REPL uses the [`domain`][] module to catch all uncaught exceptions for that REPL session. This use of the [`domain`][] module in the REPL has these side effects: * Uncaught exceptions only emit the [`'uncaughtException'`][] event in the standalone REPL. Adding a listener for this event in a REPL within another Node.js program results in [`ERR_INVALID_REPL_INPUT`][]. ```js const r = repl.start(); r.write('process.on("uncaughtException", () => console.log("Foobar"));\n'); // Output stream includes: // TypeError [ERR_INVALID_REPL_INPUT]: Listeners for `uncaughtException` // cannot be used in the REPL r.close(); ``` * Trying to use [`process.setUncaughtExceptionCaptureCallback()`][] throws an [`ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE`][] error. #### Assignment of the `_` (underscore) variable  The default evaluator will, by default, assign the result of the most recently evaluated expression to the special variable `_` (underscore). Explicitly setting `_` to a value will disable this behavior. ```console > [ 'a', 'b', 'c' ] [ 'a', 'b', 'c' ] > _.length 3 > _ += 1 Expression assignment to _ now disabled. 4 > 1 + 1 2 > _ 4 ``` Similarly, `_error` will refer to the last seen error, if there was any. Explicitly setting `_error` to a value will disable this behavior. ```console > throw new Error('foo'); Error: foo > _error.message 'foo' ``` #### `await` keyword Support for the `await` keyword is enabled at the top level. ```console > await Promise.resolve(123) 123 > await Promise.reject(new Error('REPL await')) Error: REPL await at repl:1:45 > const timeout = util.promisify(setTimeout); undefined > const old = Date.now(); await timeout(1000); console.log(Date.now() - old); 1002 undefined ``` One known limitation of using the `await` keyword in the REPL is that it will invalidate the lexical scoping of the `const` and `let` keywords. For example: ```console > const m = await Promise.resolve(123) undefined > m 123 > const m = await Promise.resolve(234) undefined > m 234 ``` [`--no-experimental-repl-await`][] shall disable top-level await in REPL. ### Reverse-i-search  The REPL supports bi-directional reverse-i-search similar to [ZSH][]. It is triggered with <kbd>Ctrl</kbd>+<kbd>R</kbd> to search backward and <kbd>Ctrl</kbd>+<kbd>S</kbd> to search forwards. Duplicated history entries will be skipped. Entries are accepted as soon as any key is pressed that doesn't correspond with the reverse search. Cancelling is possible by pressing <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>C</kbd>. Changing the direction immediately searches for the next entry in the expected direction from the current position on. ### Custom evaluation functions When a new [`repl.REPLServer`][] is created, a custom evaluation function may be provided. This can be used, for instance, to implement fully customized REPL applications. The following illustrates a hypothetical example of a REPL that performs translation of text from one language to another: ```js const repl = require('node:repl'); const { Translator } = require('translator'); const myTranslator = new Translator('en', 'fr'); function myEval(cmd, context, filename, callback) { callback(null, myTranslator.translate(cmd)); } repl.start({ prompt: '> ', eval: myEval }); ``` #### Recoverable errors At the REPL prompt, pressing <kbd>Enter</kbd> sends the current line of input to the `eval` function. In order to support multi-line input, the `eval` function can return an instance of `repl.Recoverable` to the provided callback function: ```js function myEval(cmd, context, filename, callback) { let result; try { result = vm.runInThisContext(cmd); } catch (e) { if (isRecoverableError(e)) { return callback(new repl.Recoverable(e)); } } callback(null, result); } function isRecoverableError(error) { if (error.name === 'SyntaxError') { return /^(Unexpected end of input|Unexpected token)/.test(error.message); } return false; } ``` ### Customizing REPL output By default, [`repl.REPLServer`][] instances format output using the [`util.inspect()`][] method before writing the output to the provided `Writable` stream (`process.stdout` by default). The `showProxy` inspection option is set to true by default and the `colors` option is set to true depending on the REPL's `useColors` option. The `useColors` boolean option can be specified at construction to instruct the default writer to use ANSI style codes to colorize the output from the `util.inspect()` method. If the REPL is run as standalone program, it is also possible to change the REPL's [inspection defaults][`util.inspect()`] from inside the REPL by using the `inspect.replDefaults` property which mirrors the `defaultOptions` from [`util.inspect()`][]. ```console > util.inspect.replDefaults.compact = false; false > [1] [ 1 ] > ``` To fully customize the output of a [`repl.REPLServer`][] instance pass in a new function for the `writer` option on construction. The following example, for instance, simply converts any input text to upper case: ```js const repl = require('node:repl'); const r = repl.start({ prompt: '> ', eval: myEval, writer: myWriter }); function myEval(cmd, context, filename, callback) { callback(null, cmd); } function myWriter(output) { return output.toUpperCase(); } ``` ## Class: `REPLServer`  * `options` {Object|string} See [`repl.start()`][] * Extends: {readline.Interface} Instances of `repl.REPLServer` are created using the [`repl.start()`][] method or directly using the JavaScript `new` keyword. ```js const repl = require('node:repl'); const options = { useColors: true }; const firstInstance = repl.start(options); const secondInstance = new repl.REPLServer(options); ``` ### Event: `'exit'`  The `'exit'` event is emitted when the REPL is exited either by receiving the `.exit` command as input, the user pressing <kbd>Ctrl</kbd>+<kbd>C</kbd> twice to signal `SIGINT`, or by pressing <kbd>Ctrl</kbd>+<kbd>D</kbd> to signal `'end'` on the input stream. The listener callback is invoked without any arguments. ```js replServer.on('exit', () => { console.log('Received "exit" event from repl!'); process.exit(); }); ``` ### Event: `'reset'`  The `'reset'` event is emitted when the REPL's context is reset. This occurs whenever the `.clear` command is received as input _unless_ the REPL is using the default evaluator and the `repl.REPLServer` instance was created with the `useGlobal` option set to `true`. The listener callback will be called with a reference to the `context` object as the only argument. This can be used primarily to re-initialize REPL context to some pre-defined state: ```js const repl = require('node:repl'); function initializeContext(context) { context.m = 'test'; } const r = repl.start({ prompt: '> ' }); initializeContext(r.context); r.on('reset', initializeContext); ``` When this code is executed, the global `'m'` variable can be modified but then reset to its initial value using the `.clear` command: ```console $ ./node example.js > m 'test' > m = 1 1 > m 1 > .clear Clearing context... > m 'test' > ``` ### `replServer.defineCommand(keyword, cmd)`  * `keyword` {string} The command keyword (_without_ a leading `.` character). * `cmd` {Object|Function} The function to invoke when the command is processed. The `replServer.defineCommand()` method is used to add new `.`-prefixed commands to the REPL instance. Such commands are invoked by typing a `.` followed by the `keyword`. The `cmd` is either a `Function` or an `Object` with the following properties: * `help` {string} Help text to be displayed when `.help` is entered (Optional). * `action` {Function} The function to execute, optionally accepting a single string argument. The following example shows two new commands added to the REPL instance: ```js const repl = require('node:repl'); const replServer = repl.start({ prompt: '> ' }); replServer.defineCommand('sayhello', { help: 'Say hello', action(name) { this.clearBufferedCommand(); console.log(`Hello, ${name}!`); this.displayPrompt(); } }); replServer.defineCommand('saybye', function saybye() { console.log('Goodbye!'); this.close(); }); ``` The new commands can then be used from within the REPL instance: ```console > .sayhello Node.js User Hello, Node.js User! > .saybye Goodbye! ``` ### `replServer.displayPrompt([preserveCursor])`  * `preserveCursor` {boolean} The `replServer.displayPrompt()` method readies the REPL instance for input from the user, printing the configured `prompt` to a new line in the `output` and resuming the `input` to accept new input. When multi-line input is being entered, an ellipsis is printed rather than the 'prompt'. When `preserveCursor` is `true`, the cursor placement will not be reset to `0`. The `replServer.displayPrompt` method is primarily intended to be called from within the action function for commands registered using the `replServer.defineCommand()` method. ### `replServer.clearBufferedCommand()`  The `replServer.clearBufferedCommand()` method clears any command that has been buffered but not yet executed. This method is primarily intended to be called from within the action function for commands registered using the `replServer.defineCommand()` method. ### `replServer.parseREPLKeyword(keyword[, rest])`  > Stability: 0 - Deprecated. * `keyword` {string} the potential keyword to parse and execute * `rest` {any} any parameters to the keyword command * Returns: {boolean} An internal method used to parse and execute `REPLServer` keywords. Returns `true` if `keyword` is a valid keyword, otherwise `false`. ### `replServer.setupHistory(historyPath, callback)`  * `historyPath` {string} the path to the history file * `callback` {Function} called when history writes are ready or upon error * `err` {Error} * `repl` {repl.REPLServer} Initializes a history log file for the REPL instance. When executing the Node.js binary and using the command-line REPL, a history file is initialized by default. However, this is not the case when creating a REPL programmatically. Use this method to initialize a history log file when working with REPL instances programmatically. ## `repl.builtinModules`  * {string\[]} A list of the names of all Node.js modules, e.g., `'http'`. ## `repl.start([options])`  * `options` {Object|string} * `prompt` {string} The input prompt to display. **Default:** `'> '` (with a trailing space). * `input` {stream.Readable} The `Readable` stream from which REPL input will be read. **Default:** `process.stdin`. * `output` {stream.Writable} The `Writable` stream to which REPL output will be written. **Default:** `process.stdout`. * `terminal` {boolean} If `true`, specifies that the `output` should be treated as a TTY terminal. **Default:** checking the value of the `isTTY` property on the `output` stream upon instantiation. * `eval` {Function} The function to be used when evaluating each given line of input. **Default:** an async wrapper for the JavaScript `eval()` function. An `eval` function can error with `repl.Recoverable` to indicate the input was incomplete and prompt for additional lines. * `useColors` {boolean} If `true`, specifies that the default `writer` function should include ANSI color styling to REPL output. If a custom `writer` function is provided then this has no effect. **Default:** checking color support on the `output` stream if the REPL instance's `terminal` value is `true`. * `useGlobal` {boolean} If `true`, specifies that the default evaluation function will use the JavaScript `global` as the context as opposed to creating a new separate context for the REPL instance. The node CLI REPL sets this value to `true`. **Default:** `false`. * `ignoreUndefined` {boolean} If `true`, specifies that the default writer will not output the return value of a command if it evaluates to `undefined`. **Default:** `false`. * `writer` {Function} The function to invoke to format the output of each command before writing to `output`. **Default:** [`util.inspect()`][]. * `completer` {Function} An optional function used for custom Tab auto completion. See [`readline.InterfaceCompleter`][] for an example. * `replMode` {symbol} A flag that specifies whether the default evaluator executes all JavaScript commands in strict mode or default (sloppy) mode. Acceptable values are: * `repl.REPL_MODE_SLOPPY` to evaluate expressions in sloppy mode. * `repl.REPL_MODE_STRICT` to evaluate expressions in strict mode. This is equivalent to prefacing every repl statement with `'use strict'`. * `breakEvalOnSigint` {boolean} Stop evaluating the current piece of code when `SIGINT` is received, such as when <kbd>Ctrl</kbd>+<kbd>C</kbd> is pressed. This cannot be used together with a custom `eval` function. **Default:** `false`. * `preview` {boolean} Defines if the repl prints autocomplete and output previews or not. **Default:** `true` with the default eval function and `false` in case a custom eval function is used. If `terminal` is falsy, then there are no previews and the value of `preview` has no effect. * Returns: {repl.REPLServer} The `repl.start()` method creates and starts a [`repl.REPLServer`][] instance. If `options` is a string, then it specifies the input prompt: ```js const repl = require('node:repl'); // a Unix style prompt repl.start('$ '); ``` ## The Node.js REPL Node.js itself uses the `node:repl` module to provide its own interactive interface for executing JavaScript. This can be used by executing the Node.js binary without passing any arguments (or by passing the `-i` argument): ```console $ node > const a = [1, 2, 3]; undefined > a [ 1, 2, 3 ] > a.forEach((v) => { ... console.log(v); ... }); 1 2 3 ``` ### Environment variable options Various behaviors of the Node.js REPL can be customized using the following environment variables: * `NODE_REPL_HISTORY`: When a valid path is given, persistent REPL history will be saved to the specified file rather than `.node_repl_history` in the user's home directory. Setting this value to `''` (an empty string) will disable persistent REPL history. Whitespace will be trimmed from the value. On Windows platforms environment variables with empty values are invalid so set this variable to one or more spaces to disable persistent REPL history. * `NODE_REPL_HISTORY_SIZE`: Controls how many lines of history will be persisted if history is available. Must be a positive number. **Default:** `1000`. * `NODE_REPL_MODE`: May be either `'sloppy'` or `'strict'`. **Default:** `'sloppy'`, which will allow non-strict mode code to be run. ### Persistent history By default, the Node.js REPL will persist history between `node` REPL sessions by saving inputs to a `.node_repl_history` file located in the user's home directory. This can be disabled by setting the environment variable `NODE_REPL_HISTORY=''`. ### Using the Node.js REPL with advanced line-editors For advanced line-editors, start Node.js with the environment variable `NODE_NO_READLINE=1`. This will start the main and debugger REPL in canonical terminal settings, which will allow use with `rlwrap`. For example, the following can be added to a `.bashrc` file: ```text alias node="env NODE_NO_READLINE=1 rlwrap node" ``` ### Starting multiple REPL instances against a single running instance It is possible to create and run multiple REPL instances against a single running instance of Node.js that share a single `global` object but have separate I/O interfaces. The following example, for instance, provides separate REPLs on `stdin`, a Unix socket, and a TCP socket: ```js const net = require('node:net'); const repl = require('node:repl'); let connections = 0; repl.start({ prompt: 'Node.js via stdin> ', input: process.stdin, output: process.stdout }); net.createServer((socket) => { connections += 1; repl.start({ prompt: 'Node.js via Unix socket> ', input: socket, output: socket }).on('exit', () => { socket.end(); }); }).listen('/tmp/node-repl-sock'); net.createServer((socket) => { connections += 1; repl.start({ prompt: 'Node.js via TCP socket> ', input: socket, output: socket }).on('exit', () => { socket.end(); }); }).listen(5001); ``` Running this application from the command line will start a REPL on stdin. Other REPL clients may connect through the Unix socket or TCP socket. `telnet`, for instance, is useful for connecting to TCP sockets, while `socat` can be used to connect to both Unix and TCP sockets. By starting a REPL from a Unix socket-based server instead of stdin, it is possible to connect to a long-running Node.js process without restarting it. For an example of running a "full-featured" (`terminal`) REPL over a `net.Server` and `net.Socket` instance, see: <https://gist.github.com/TooTallNate/2209310>. For an example of running a REPL instance over [`curl(1)`][], see: <https://gist.github.com/TooTallNate/2053342>. [TTY keybindings]: readline.md#tty-keybindings [ZSH]: https://en.wikipedia.org/wiki/Z_shell [`'uncaughtException'`]: process.md#event-uncaughtexception [`--no-experimental-repl-await`]: cli.md#--no-experimental-repl-await [`ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE`]: errors.md#err_domain_cannot_set_uncaught_exception_capture [`ERR_INVALID_REPL_INPUT`]: errors.md#err_invalid_repl_input [`curl(1)`]: https://curl.haxx.se/docs/manpage.html [`domain`]: domain.md [`process.setUncaughtExceptionCaptureCallback()`]: process.md#processsetuncaughtexceptioncapturecallbackfn [`readline.InterfaceCompleter`]: readline.md#use-of-the-completer-function [`repl.ReplServer`]: #class-replserver [`repl.start()`]: #replstartoptions [`reverse-i-search`]: #reverse-i-search [`util.inspect()`]: util.md#utilinspectobject-options [stream]: stream.md

Name	Size	Last Modified	Owner	Permissions	Options
..	--	October 23 2023 6:29:41	root	0755
assets	--	October 23 2023 6:29:41	root	0755

addons.html	103.732 KB	August 09 2023 12:32:55	root	0644
addons.json.gz	10.921 KB	August 09 2023 12:32:55	root	0644
addons.md	39.649 KB	August 09 2023 12:32:55	root	0644
all.html	6.72 MB	August 09 2023 12:32:55	root	0644
all.json.gz	839.889 KB	August 09 2023 12:32:55	root	0644
assert.html	188.064 KB	August 09 2023 12:32:55	root	0644
assert.json.gz	12.917 KB	August 09 2023 12:32:55	root	0644
assert.md	65.666 KB	August 09 2023 12:32:55	root	0644
async_context.html	78.018 KB	August 09 2023 12:32:55	root	0644
async_context.json.gz	6.719 KB	August 09 2023 12:32:55	root	0644
async_context.md	22.997 KB	August 09 2023 12:32:55	root	0644
async_hooks.html	80.186 KB	August 09 2023 12:32:55	root	0644
async_hooks.json.gz	9.531 KB	August 09 2023 12:32:55	root	0644
async_hooks.md	28.223 KB	August 09 2023 12:32:55	root	0644
buffer.html	462.769 KB	August 09 2023 12:32:55	root	0644
buffer.json.gz	27.512 KB	August 09 2023 12:32:55	root	0644
buffer.md	145.345 KB	August 09 2023 12:32:55	root	0644
child_process.html	166.773 KB	August 09 2023 12:32:55	root	0644
child_process.json.gz	20.828 KB	August 09 2023 12:32:55	root	0644
child_process.md	70.11 KB	August 09 2023 12:32:55	root	0644
cli.html	140.843 KB	August 09 2023 12:32:55	root	0644
cli.json.gz	21.876 KB	August 09 2023 12:32:55	root	0644
cli.md	57.601 KB	August 09 2023 12:32:55	root	0644
cluster.html	89.359 KB	August 09 2023 12:32:55	root	0644
cluster.json.gz	9.523 KB	August 09 2023 12:32:55	root	0644
cluster.md	28.754 KB	August 09 2023 12:32:55	root	0644
console.html	58.51 KB	August 09 2023 12:32:55	root	0644
console.json.gz	6.067 KB	August 09 2023 12:32:55	root	0644
console.md	16.495 KB	August 09 2023 12:32:55	root	0644
corepack.html	21.889 KB	August 09 2023 12:32:55	root	0644
corepack.json.gz	2.512 KB	August 09 2023 12:32:55	root	0644
corepack.md	4.951 KB	August 09 2023 12:32:55	root	0644
crypto.html	515.748 KB	August 09 2023 12:32:55	root	0644
crypto.json.gz	44.629 KB	August 09 2023 12:32:55	root	0644
crypto.md	189.668 KB	August 09 2023 12:32:55	root	0644
debugger.html	27.063 KB	August 09 2023 12:32:55	root	0644
debugger.json.gz	2.979 KB	August 09 2023 12:32:55	root	0644
debugger.md	6.509 KB	August 09 2023 12:32:55	root	0644
deprecations.html	191.997 KB	August 09 2023 12:32:55	root	0644
deprecations.json.gz	22.844 KB	August 09 2023 12:32:55	root	0644
deprecations.md	93.906 KB	August 09 2023 12:32:55	root	0644
dgram.html	88.111 KB	August 09 2023 12:32:55	root	0644
dgram.json.gz	9.951 KB	August 09 2023 12:32:55	root	0644
dgram.md	30.256 KB	August 09 2023 12:32:55	root	0644
diagnostics_channel.html	44.865 KB	August 09 2023 12:32:55	root	0644
diagnostics_channel.json.gz	3.183 KB	August 09 2023 12:32:55	root	0644
diagnostics_channel.md	10.99 KB	August 09 2023 12:32:55	root	0644
dns.html	122.021 KB	August 09 2023 12:32:55	root	0644
dns.json.gz	15.265 KB	August 09 2023 12:32:55	root	0644
dns.md	47.228 KB	August 09 2023 12:32:55	root	0644
documentation.html	24.487 KB	August 09 2023 12:32:55	root	0644
documentation.json.gz	2.1 KB	August 09 2023 12:32:55	root	0644
documentation.md	4.471 KB	August 09 2023 12:32:55	root	0644
domain.html	47.881 KB	August 09 2023 12:32:55	root	0644
domain.json.gz	6.203 KB	August 09 2023 12:32:55	root	0644
domain.md	15.205 KB	August 09 2023 12:32:55	root	0644
embedding.html	25.116 KB	August 09 2023 12:32:55	root	0644
embedding.json.gz	2.931 KB	August 09 2023 12:32:55	root	0644
embedding.md	6.466 KB	August 09 2023 12:32:55	root	0644
errors.html	275.354 KB	August 09 2023 12:32:55	root	0644
errors.json.gz	41.519 KB	August 09 2023 12:32:55	root	0644
errors.md	94.822 KB	August 09 2023 12:32:55	root	0644
esm.html	125.451 KB	August 09 2023 12:32:55	root	0644
esm.json.gz	20.241 KB	August 09 2023 12:32:55	root	0644
esm.md	58.762 KB	August 09 2023 12:32:55	root	0644
events.html	186.533 KB	August 09 2023 12:32:55	root	0644
events.json.gz	15.857 KB	August 09 2023 12:32:55	root	0644
events.md	55.578 KB	August 09 2023 12:32:55	root	0644
fs.html	585.922 KB	August 09 2023 12:32:55	root	0644
fs.json.gz	63.869 KB	August 09 2023 12:32:55	root	0644
fs.md	227.271 KB	August 09 2023 12:32:55	root	0644
globals.html	54.78 KB	August 09 2023 12:32:55	root	0644
globals.json.gz	5.521 KB	August 09 2023 12:32:55	root	0644
globals.md	13.758 KB	August 09 2023 12:32:55	root	0644
http.html	257.352 KB	August 09 2023 12:32:55	root	0644
http.json.gz	33.471 KB	August 09 2023 12:32:55	root	0644
http.md	99.305 KB	August 09 2023 12:32:55	root	0644
http2.html	310.105 KB	August 09 2023 12:32:55	root	0644
http2.json.gz	38.246 KB	August 09 2023 12:32:55	root	0644
http2.md	126.901 KB	August 09 2023 12:32:55	root	0644
https.html	54.206 KB	August 09 2023 12:32:55	root	0644
https.json.gz	5.581 KB	August 09 2023 12:32:55	root	0644
https.md	15.709 KB	August 09 2023 12:32:55	root	0644
index.html	12.408 KB	August 09 2023 12:32:55	root	0644
index.json	0.053 KB	August 09 2023 12:32:55	root	0644
index.md	1.905 KB	August 09 2023 12:32:55	root	0644
inspector.html	32.761 KB	August 09 2023 12:32:55	root	0644
inspector.json.gz	3.355 KB	August 09 2023 12:32:55	root	0644
inspector.md	6.931 KB	August 09 2023 12:32:55	root	0644
intl.html	31.391 KB	August 09 2023 12:32:55	root	0644
intl.json.gz	3.865 KB	August 09 2023 12:32:55	root	0644
intl.md	10.715 KB	August 09 2023 12:32:55	root	0644
module.html	30.263 KB	August 09 2023 12:32:55	root	0644
module.json.gz	2.667 KB	August 09 2023 12:32:55	root	0644
module.md	5.03 KB	August 09 2023 12:32:55	root	0644
modules.html	79.392 KB	August 09 2023 12:32:55	root	0644
modules.json.gz	12.682 KB	August 09 2023 12:32:55	root	0644
modules.md	33.09 KB	August 09 2023 12:32:55	root	0644
n-api.html	383.687 KB	August 09 2023 12:32:55	root	0644
n-api.json.gz	49.905 KB	August 09 2023 12:32:55	root	0644
n-api.md	212.467 KB	August 09 2023 12:32:55	root	0644
net.html	135.688 KB	August 09 2023 12:32:55	root	0644
net.json.gz	16.709 KB	August 09 2023 12:32:55	root	0644
net.md	47.822 KB	August 09 2023 12:32:55	root	0644
os.html	69.783 KB	August 09 2023 12:32:55	root	0644
os.json.gz	8.566 KB	August 09 2023 12:32:55	root	0644
os.md	34.489 KB	August 09 2023 12:32:55	root	0644
packages.html	98.842 KB	August 09 2023 12:32:55	root	0644
packages.json.gz	15.398 KB	August 09 2023 12:32:55	root	0644
packages.md	46.294 KB	August 09 2023 12:32:55	root	0644
path.html	51.026 KB	August 09 2023 12:32:55	root	0644
path.json.gz	4.9 KB	August 09 2023 12:32:55	root	0644
path.md	14.905 KB	August 09 2023 12:32:55	root	0644
perf_hooks.html	136.052 KB	August 09 2023 12:32:55	root	0644
perf_hooks.json.gz	12.18 KB	August 09 2023 12:32:55	root	0644
perf_hooks.md	40.914 KB	August 09 2023 12:32:55	root	0644
permissions.html	43.819 KB	August 09 2023 12:32:55	root	0644
permissions.json.gz	5.438 KB	August 09 2023 12:32:55	root	0644
permissions.md	14.591 KB	August 09 2023 12:32:55	root	0644
policy.html	13.945 KB	August 09 2023 12:32:55	root	0644
policy.json	0.464 KB	August 09 2023 12:32:55	root	0644
policy.md	0.216 KB	August 09 2023 12:32:55	root	0644
process.html	283.726 KB	August 09 2023 12:32:55	root	0644
process.json.gz	30.81 KB	August 09 2023 12:32:55	root	0644
process.md	105.606 KB	August 09 2023 12:32:55	root	0644
punycode.html	25.688 KB	August 09 2023 12:32:55	root	0644
punycode.json.gz	1.995 KB	August 09 2023 12:32:55	root	0644
punycode.md	4.175 KB	August 09 2023 12:32:55	root	0644
querystring.html	27.652 KB	August 09 2023 12:32:55	root	0644
querystring.json.gz	2.62 KB	August 09 2023 12:32:55	root	0644
querystring.md	5.504 KB	August 09 2023 12:32:55	root	0644
readline.html	78.159 KB	August 09 2023 12:32:55	root	0644
readline.json.gz	9.782 KB	August 09 2023 12:32:55	root	0644
readline.md	28.027 KB	August 09 2023 12:32:55	root	0644
repl.html	67.367 KB	August 09 2023 12:32:55	root	0644
repl.json.gz	9.993 KB	August 09 2023 12:32:55	root	0644
repl.md	23.665 KB	August 09 2023 12:32:55	root	0644
report.html	78.951 KB	August 09 2023 12:32:55	root	0644
report.json.gz	6.198 KB	August 09 2023 12:32:55	root	0644
report.md	18.202 KB	August 09 2023 12:32:55	root	0644
stream.html	346.823 KB	August 09 2023 12:32:55	root	0644
stream.json.gz	46.987 KB	August 09 2023 12:32:55	root	0644
stream.md	133.766 KB	August 09 2023 12:32:55	root	0644
string_decoder.html	22.827 KB	August 09 2023 12:32:55	root	0644
string_decoder.json.gz	1.545 KB	August 09 2023 12:32:55	root	0644
string_decoder.md	2.957 KB	August 09 2023 12:32:55	root	0644
synopsis.html	19.031 KB	August 09 2023 12:32:55	root	0644
synopsis.json	2.956 KB	August 09 2023 12:32:55	root	0644
synopsis.md	2.117 KB	August 09 2023 12:32:55	root	0644
test.html	85.498 KB	August 09 2023 12:32:55	root	0644
test.json.gz	8.704 KB	August 09 2023 12:32:55	root	0644
test.md	28.898 KB	August 09 2023 12:32:55	root	0644
timers.html	54.066 KB	August 09 2023 12:32:55	root	0644
timers.json.gz	5.042 KB	August 09 2023 12:32:55	root	0644
timers.md	14.62 KB	August 09 2023 12:32:55	root	0644
tls.html	174.438 KB	August 09 2023 12:32:55	root	0644
tls.json.gz	31.448 KB	August 09 2023 12:32:55	root	0644
tls.md	85.361 KB	August 09 2023 12:32:55	root	0644
tracing.html	33.333 KB	August 09 2023 12:32:55	root	0644
tracing.json.gz	3.4 KB	August 09 2023 12:32:55	root	0644
tracing.md	8.229 KB	August 09 2023 12:32:55	root	0644
tty.html	36.365 KB	August 09 2023 12:32:55	root	0644
tty.json.gz	3.66 KB	August 09 2023 12:32:55	root	0644
tty.md	8.777 KB	August 09 2023 12:32:55	root	0644
url.html	144.705 KB	August 09 2023 12:32:55	root	0644
url.json.gz	15.334 KB	August 09 2023 12:32:55	root	0644
url.md	52.175 KB	August 09 2023 12:32:55	root	0644
util.html	241.566 KB	August 09 2023 12:32:55	root	0644
util.json.gz	23.489 KB	August 09 2023 12:32:55	root	0644
util.md	85.895 KB	August 09 2023 12:32:55	root	0644
v8.html	96.239 KB	August 09 2023 12:32:55	root	0644
v8.json.gz	10.732 KB	August 09 2023 12:32:55	root	0644
v8.md	30.479 KB	August 09 2023 12:32:55	root	0644
vm.html	138.64 KB	August 09 2023 12:32:55	root	0644
vm.json.gz	16.511 KB	August 09 2023 12:32:55	root	0644
vm.md	58.484 KB	August 09 2023 12:32:55	root	0644
wasi.html	27.627 KB	August 09 2023 12:32:55	root	0644
wasi.json.gz	2.897 KB	August 09 2023 12:32:55	root	0644
wasi.md	6.621 KB	August 09 2023 12:32:55	root	0644
webcrypto.html	147.224 KB	August 09 2023 12:32:55	root	0644
webcrypto.json.gz	9.508 KB	August 09 2023 12:32:55	root	0644
webcrypto.md	41.691 KB	August 09 2023 12:32:55	root	0644
webstreams.html	142.197 KB	August 09 2023 12:32:55	root	0644
webstreams.json.gz	9.602 KB	August 09 2023 12:32:55	root	0644
webstreams.md	33.873 KB	August 09 2023 12:32:55	root	0644
worker_threads.html	111.69 KB	August 09 2023 12:32:55	root	0644
worker_threads.json.gz	14.308 KB	August 09 2023 12:32:55	root	0644
worker_threads.md	42.578 KB	August 09 2023 12:32:55	root	0644
zlib.html	108.132 KB	August 09 2023 12:32:55	root	0644
zlib.json.gz	10.342 KB	August 09 2023 12:32:55	root	0644
zlib.md	35.097 KB	August 09 2023 12:32:55	root	0644

NineSec Team - 2022