Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 3.15.22.202
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
www /
unp-musonza /
node_modules /
loose-envify /
Delete
Unzip
Name
Size
Permission
Date
Action
LICENSE
1.07
KB
-rw-r--r--
1985-10-26 08:15
README.md
1.05
KB
-rw-r--r--
1985-10-26 08:15
cli.js
356
B
-rwxr-xr-x
1985-10-26 08:15
custom.js
83
B
-rw-r--r--
1985-10-26 08:15
index.js
72
B
-rw-r--r--
1985-10-26 08:15
loose-envify.js
791
B
-rw-r--r--
1985-10-26 08:15
package.json
1.65
KB
-rw-r--r--
2021-02-04 21:24
replace.js
1.5
KB
-rw-r--r--
1985-10-26 08:15
Save
Rename
# loose-envify [](https://travis-ci.org/zertosh/loose-envify) Fast (and loose) selective `process.env` replacer using [js-tokens](https://github.com/lydell/js-tokens) instead of an AST. Works just like [envify](https://github.com/hughsk/envify) but much faster. ## Gotchas * Doesn't handle broken syntax. * Doesn't look inside embedded expressions in template strings. - **this won't work:** ```js console.log(`the current env is ${process.env.NODE_ENV}`); ``` * Doesn't replace oddly-spaced or oddly-commented expressions. - **this won't work:** ```js console.log(process./*won't*/env./*work*/NODE_ENV); ``` ## Usage/Options loose-envify has the exact same interface as [envify](https://github.com/hughsk/envify), including the CLI. ## Benchmark ``` envify: $ for i in {1..5}; do node bench/bench.js 'envify'; done 708ms 727ms 791ms 719ms 720ms loose-envify: $ for i in {1..5}; do node bench/bench.js '../'; done 51ms 52ms 52ms 52ms 52ms ```