Linux localhost 5.4.0-198-generic #218-Ubuntu SMP Fri Sep 27 20:18:53 UTC 2024 x86_64
Apache/2.4.41 (Ubuntu)
: 23.92.16.63 | : 104.23.253.119
Cant Read [ /etc/named.conf ]
8.1.5
www-data
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
nodejs /
api /
[ HOME SHELL ]
Name
Size
Permission
Action
assets
[ DIR ]
drwxr-xr-x
addons.html
105.72
KB
-rw-r--r--
addons.json.gz
10.95
KB
-rw-r--r--
addons.md
39.76
KB
-rw-r--r--
all.html
7.2
MB
-rw-r--r--
all.json.gz
881.44
KB
-rw-r--r--
assert.html
191.3
KB
-rw-r--r--
assert.json.gz
13
KB
-rw-r--r--
assert.md
66.51
KB
-rw-r--r--
async_context.html
84.04
KB
-rw-r--r--
async_context.json.gz
7.09
KB
-rw-r--r--
async_context.md
24.68
KB
-rw-r--r--
async_hooks.html
87.13
KB
-rw-r--r--
async_hooks.json.gz
9.82
KB
-rw-r--r--
async_hooks.md
30.48
KB
-rw-r--r--
buffer.html
479.09
KB
-rw-r--r--
buffer.json.gz
28.89
KB
-rw-r--r--
buffer.md
148.96
KB
-rw-r--r--
child_process.html
168.62
KB
-rw-r--r--
child_process.json.gz
20.9
KB
-rw-r--r--
child_process.md
70.54
KB
-rw-r--r--
cli.html
154.13
KB
-rw-r--r--
cli.json.gz
23.79
KB
-rw-r--r--
cli.md
63.8
KB
-rw-r--r--
cluster.html
90.59
KB
-rw-r--r--
cluster.json.gz
9.48
KB
-rw-r--r--
cluster.md
28.84
KB
-rw-r--r--
console.html
59.43
KB
-rw-r--r--
console.json.gz
6.07
KB
-rw-r--r--
console.md
16.5
KB
-rw-r--r--
corepack.html
22.56
KB
-rw-r--r--
corepack.json.gz
2.55
KB
-rw-r--r--
corepack.md
5.08
KB
-rw-r--r--
crypto.html
521.88
KB
-rw-r--r--
crypto.json.gz
45.72
KB
-rw-r--r--
crypto.md
193.91
KB
-rw-r--r--
debugger.html
28.15
KB
-rw-r--r--
debugger.json.gz
3.12
KB
-rw-r--r--
debugger.md
7.02
KB
-rw-r--r--
deprecations.html
197.6
KB
-rw-r--r--
deprecations.json.gz
23.7
KB
-rw-r--r--
deprecations.md
97.51
KB
-rw-r--r--
dgram.html
89.39
KB
-rw-r--r--
dgram.json.gz
10.07
KB
-rw-r--r--
dgram.md
30.76
KB
-rw-r--r--
diagnostics_channel.html
44.76
KB
-rw-r--r--
diagnostics_channel.json.gz
3.2
KB
-rw-r--r--
diagnostics_channel.md
11.09
KB
-rw-r--r--
dns.html
130.7
KB
-rw-r--r--
dns.json.gz
15.74
KB
-rw-r--r--
dns.md
52.17
KB
-rw-r--r--
documentation.html
25.04
KB
-rw-r--r--
documentation.json.gz
2.22
KB
-rw-r--r--
documentation.md
4.67
KB
-rw-r--r--
domain.html
48.47
KB
-rw-r--r--
domain.json.gz
6.2
KB
-rw-r--r--
domain.md
15.21
KB
-rw-r--r--
embedding.html
25.79
KB
-rw-r--r--
embedding.json.gz
3.01
KB
-rw-r--r--
embedding.md
6.65
KB
-rw-r--r--
errors.html
282.1
KB
-rw-r--r--
errors.json.gz
42.26
KB
-rw-r--r--
errors.md
96.75
KB
-rw-r--r--
esm.html
126.92
KB
-rw-r--r--
esm.json.gz
20.56
KB
-rw-r--r--
esm.md
58.28
KB
-rw-r--r--
events.html
225.71
KB
-rw-r--r--
events.json.gz
16.69
KB
-rw-r--r--
events.md
64.93
KB
-rw-r--r--
fs.html
628.53
KB
-rw-r--r--
fs.json.gz
66.73
KB
-rw-r--r--
fs.md
247.34
KB
-rw-r--r--
globals.html
74.86
KB
-rw-r--r--
globals.json.gz
9
KB
-rw-r--r--
globals.md
20.04
KB
-rw-r--r--
http.html
275.03
KB
-rw-r--r--
http.json.gz
35.28
KB
-rw-r--r--
http.md
106.51
KB
-rw-r--r--
http2.html
318.05
KB
-rw-r--r--
http2.json.gz
39.24
KB
-rw-r--r--
http2.md
129.92
KB
-rw-r--r--
https.html
56.48
KB
-rw-r--r--
https.json.gz
5.69
KB
-rw-r--r--
https.md
16.33
KB
-rw-r--r--
index.html
12.63
KB
-rw-r--r--
index.json
54
B
-rw-r--r--
index.md
1.97
KB
-rw-r--r--
inspector.html
34.25
KB
-rw-r--r--
inspector.json.gz
3.62
KB
-rw-r--r--
inspector.md
7.63
KB
-rw-r--r--
intl.html
31.9
KB
-rw-r--r--
intl.json.gz
3.87
KB
-rw-r--r--
intl.md
10.71
KB
-rw-r--r--
module.html
30.94
KB
-rw-r--r--
module.json.gz
2.7
KB
-rw-r--r--
module.md
5.12
KB
-rw-r--r--
modules.html
80.58
KB
-rw-r--r--
modules.json.gz
12.65
KB
-rw-r--r--
modules.md
32.97
KB
-rw-r--r--
n-api.html
395.21
KB
-rw-r--r--
n-api.json.gz
50.69
KB
-rw-r--r--
n-api.md
214.45
KB
-rw-r--r--
net.html
140.93
KB
-rw-r--r--
net.json.gz
17.64
KB
-rw-r--r--
net.md
50.96
KB
-rw-r--r--
os.html
71.85
KB
-rw-r--r--
os.json.gz
8.88
KB
-rw-r--r--
os.md
35.5
KB
-rw-r--r--
packages.html
99.12
KB
-rw-r--r--
packages.json.gz
15.18
KB
-rw-r--r--
packages.md
45.48
KB
-rw-r--r--
path.html
52.44
KB
-rw-r--r--
path.json.gz
4.9
KB
-rw-r--r--
path.md
14.91
KB
-rw-r--r--
perf_hooks.html
139.88
KB
-rw-r--r--
perf_hooks.json.gz
12.51
KB
-rw-r--r--
perf_hooks.md
42.15
KB
-rw-r--r--
permissions.html
44.6
KB
-rw-r--r--
permissions.json.gz
5.44
KB
-rw-r--r--
permissions.md
14.59
KB
-rw-r--r--
policy.html
14.21
KB
-rw-r--r--
policy.json
475
B
-rw-r--r--
policy.md
221
B
-rw-r--r--
process.html
290.1
KB
-rw-r--r--
process.json.gz
31.21
KB
-rw-r--r--
process.md
106.75
KB
-rw-r--r--
punycode.html
26.24
KB
-rw-r--r--
punycode.json.gz
2
KB
-rw-r--r--
punycode.md
4.17
KB
-rw-r--r--
querystring.html
28.24
KB
-rw-r--r--
querystring.json.gz
2.65
KB
-rw-r--r--
querystring.md
5.57
KB
-rw-r--r--
readline.html
109.24
KB
-rw-r--r--
readline.json.gz
11.9
KB
-rw-r--r--
readline.md
40.45
KB
-rw-r--r--
repl.html
68.72
KB
-rw-r--r--
repl.json.gz
10
KB
-rw-r--r--
repl.md
23.69
KB
-rw-r--r--
report.html
81.54
KB
-rw-r--r--
report.json.gz
6.39
KB
-rw-r--r--
report.md
18.83
KB
-rw-r--r--
single-executable-applications...
23.53
KB
-rw-r--r--
single-executable-applications...
2.36
KB
-rw-r--r--
single-executable-applications...
5.12
KB
-rw-r--r--
stream.html
397.04
KB
-rw-r--r--
stream.json.gz
51.16
KB
-rw-r--r--
stream.md
145.8
KB
-rw-r--r--
string_decoder.html
23.21
KB
-rw-r--r--
string_decoder.json.gz
1.54
KB
-rw-r--r--
string_decoder.md
2.96
KB
-rw-r--r--
synopsis.html
19.54
KB
-rw-r--r--
synopsis.json
2.96
KB
-rw-r--r--
synopsis.md
2.12
KB
-rw-r--r--
test.html
168.11
KB
-rw-r--r--
test.json.gz
16.62
KB
-rw-r--r--
test.md
57.47
KB
-rw-r--r--
timers.html
55.89
KB
-rw-r--r--
timers.json.gz
5.21
KB
-rw-r--r--
timers.md
15.53
KB
-rw-r--r--
tls.html
179.78
KB
-rw-r--r--
tls.json.gz
32.31
KB
-rw-r--r--
tls.md
87.96
KB
-rw-r--r--
tracing.html
34.37
KB
-rw-r--r--
tracing.json.gz
3.47
KB
-rw-r--r--
tracing.md
8.52
KB
-rw-r--r--
tty.html
36.94
KB
-rw-r--r--
tty.json.gz
3.72
KB
-rw-r--r--
tty.md
8.91
KB
-rw-r--r--
url.html
150.42
KB
-rw-r--r--
url.json.gz
15.7
KB
-rw-r--r--
url.md
53.65
KB
-rw-r--r--
util.html
285.68
KB
-rw-r--r--
util.json.gz
25.73
KB
-rw-r--r--
util.md
96.25
KB
-rw-r--r--
v8.html
111.35
KB
-rw-r--r--
v8.json.gz
11.86
KB
-rw-r--r--
v8.md
34.31
KB
-rw-r--r--
vm.html
142.53
KB
-rw-r--r--
vm.json.gz
16.81
KB
-rw-r--r--
vm.md
59.81
KB
-rw-r--r--
wasi.html
27.91
KB
-rw-r--r--
wasi.json.gz
2.86
KB
-rw-r--r--
wasi.md
6.54
KB
-rw-r--r--
webcrypto.html
152.21
KB
-rw-r--r--
webcrypto.json.gz
9.76
KB
-rw-r--r--
webcrypto.md
45.48
KB
-rw-r--r--
webstreams.html
150.7
KB
-rw-r--r--
webstreams.json.gz
9.88
KB
-rw-r--r--
webstreams.md
36.82
KB
-rw-r--r--
worker_threads.html
113.35
KB
-rw-r--r--
worker_threads.json.gz
14.43
KB
-rw-r--r--
worker_threads.md
43.13
KB
-rw-r--r--
zlib.html
108.85
KB
-rw-r--r--
zlib.json.gz
10.34
KB
-rw-r--r--
zlib.md
35.1
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : single-executable-applications.md
# Single executable applications <!--introduced_in=v18.16.0--> <!-- YAML added: - v19.7.0 - v18.16.0 --> > Stability: 1 - Experimental: This feature is being designed and will change. <!-- source_link=src/node_sea.cc --> This feature allows the distribution of a Node.js application conveniently to a system that does not have Node.js installed. Node.js supports the creation of [single executable applications][] by allowing the injection of a JavaScript file into the `node` binary. During start up, the program checks if anything has been injected. If the script is found, it executes its contents. Otherwise Node.js operates as it normally does. The single executable application feature only supports running a single embedded [CommonJS][] file. A bundled JavaScript file can be turned into a single executable application with any tool which can inject resources into the `node` binary. Here are the steps for creating a single executable application using one such tool, [postject][]: 1. Create a JavaScript file: ```console $ echo 'console.log(`Hello, ${process.argv[2]}!`);' > hello.js ``` 2. Create a copy of the `node` executable and name it according to your needs: ```console $ cp $(command -v node) hello ``` 3. Inject the JavaScript file into the copied binary by running `postject` with the following options: * `hello` - The name of the copy of the `node` executable created in step 2. * `NODE_JS_CODE` - The name of the resource / note / section in the binary where the contents of the JavaScript file will be stored. * `hello.js` - The name of the JavaScript file created in step 1. * `--sentinel-fuse NODE_JS_FUSE_fce680ab2cc467b6e072b8b5df1996b2` - The [fuse][] used by the Node.js project to detect if a file has been injected. * `--macho-segment-name NODE_JS` (only needed on macOS) - The name of the segment in the binary where the contents of the JavaScript file will be stored. To summarize, here is the required command for each platform: * On systems other than macOS: ```console $ npx postject hello NODE_JS_CODE hello.js \ --sentinel-fuse NODE_JS_FUSE_fce680ab2cc467b6e072b8b5df1996b2 ``` * On macOS: ```console $ npx postject hello NODE_JS_CODE hello.js \ --sentinel-fuse NODE_JS_FUSE_fce680ab2cc467b6e072b8b5df1996b2 \ --macho-segment-name NODE_JS ``` 4. Run the binary: ```console $ ./hello world Hello, world! ``` ## Notes ### `require(id)` in the injected module is not file based `require()` in the injected module is not the same as the [`require()`][] available to modules that are not injected. It also does not have any of the properties that non-injected [`require()`][] has except [`require.main`][]. It can only be used to load built-in modules. Attempting to load a module that can only be found in the file system will throw an error. Instead of relying on a file based `require()`, users can bundle their application into a standalone JavaScript file to inject into the executable. This also ensures a more deterministic dependency graph. However, if a file based `require()` is still needed, that can also be achieved: ```js const { createRequire } = require('node:module'); require = createRequire(__filename); ``` ### `__filename` and `module.filename` in the injected module The values of `__filename` and `module.filename` in the injected module are equal to [`process.execPath`][]. ### `__dirname` in the injected module The value of `__dirname` in the injected module is equal to the directory name of [`process.execPath`][]. ### Single executable application creation process A tool aiming to create a single executable Node.js application must inject the contents of a JavaScript file into: * a resource named `NODE_JS_CODE` if the `node` binary is a [PE][] file * a section named `NODE_JS_CODE` in the `NODE_JS` segment if the `node` binary is a [Mach-O][] file * a note named `NODE_JS_CODE` if the `node` binary is an [ELF][] file Search the binary for the `NODE_JS_FUSE_fce680ab2cc467b6e072b8b5df1996b2:0` [fuse][] string and flip the last character to `1` to indicate that a resource has been injected. ### Platform support Single-executable support is tested regularly on CI only on the following platforms: * Windows * macOS * Linux (AMD64 only) This is due to a lack of better tools to generate single-executables that can be used to test this feature on other platforms. Suggestions for other resource injection tools/workflows are welcomed. Please start a discussion at <https://github.com/nodejs/single-executable/discussions> to help us document them. [CommonJS]: modules.md#modules-commonjs-modules [ELF]: https://en.wikipedia.org/wiki/Executable_and_Linkable_Format [Mach-O]: https://en.wikipedia.org/wiki/Mach-O [PE]: https://en.wikipedia.org/wiki/Portable_Executable [`process.execPath`]: process.md#processexecpath [`require()`]: modules.md#requireid [`require.main`]: modules.md#accessing-the-main-module [fuse]: https://www.electronjs.org/docs/latest/tutorial/fuses [postject]: https://github.com/nodejs/postject [single executable applications]: https://github.com/nodejs/single-executable
Close