Linux premium71.web-hosting.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64
LiteSpeed
Server IP : 198.187.29.8 & Your IP : 18.117.189.91
Domains :
Cant Read [ /etc/named.conf ]
User : cleahvkv
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
lib /
node_modules /
npm /
node_modules /
read-cmd-shim /
Delete
Unzip
Name
Size
Permission
Date
Action
LICENSE
752
B
-rw-r--r--
2021-03-10 14:36
README.md
1.12
KB
-rw-r--r--
2021-03-10 14:36
index.js
1.73
KB
-rw-r--r--
2021-03-10 14:36
package.json
1.65
KB
-rw-r--r--
2021-03-10 14:36
Save
Rename
# read-cmd-shim Figure out what a [`cmd-shim`](https://github.com/ForbesLindesay/cmd-shim) is pointing at. This acts as the equivalent of [`fs.readlink`](https://nodejs.org/api/fs.html#fs_fs_readlink_path_callback). ### Usage ``` var readCmdShim = require('read-cmd-shim') readCmdShim('/path/to/shim.cmd', function (er, destination) { … }) var destination = readCmdShim.sync('/path/to/shim.cmd') ``` ### readCmdShim(path, callback) Reads the `cmd-shim` located at `path` and calls back with the _relative_ path that the shim points at. Consider this as roughly the equivalent of `fs.readlink`. This can read both `.cmd` style that are run by the Windows Command Prompt and Powershell, and the kind without any extension that are used by Cygwin. This can return errors that `fs.readFile` returns, except that they'll include a stack trace from where `readCmdShim` was called. Plus it can return a special `ENOTASHIM` exception, when it can't find a cmd-shim in the file referenced by `path`. This should only happen if you pass in a non-command shim. ### readCmdShim.sync(path) Same as above but synchronous. Errors are thrown.