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 /
resolve-cwd /
Delete
Unzip
Name
Size
Permission
Date
Action
index.js
208
B
-rw-r--r--
2017-04-28 09:13
license
1.09
KB
-rw-r--r--
2016-10-25 19:01
package.json
1.62
KB
-rw-r--r--
2021-02-04 21:24
readme.md
1.44
KB
-rw-r--r--
2017-04-28 09:07
Save
Rename
# resolve-cwd [](https://travis-ci.org/sindresorhus/resolve-cwd) > Resolve the path of a module like [`require.resolve()`](https://nodejs.org/api/globals.html#globals_require_resolve) but from the current working directory ## Install ``` $ npm install --save resolve-cwd ``` ## Usage ```js const resolveCwd = require('resolve-cwd'); console.log(__dirname); //=> '/Users/sindresorhus/rainbow' console.log(process.cwd()); //=> '/Users/sindresorhus/unicorn' resolveCwd('./foo'); //=> '/Users/sindresorhus/unicorn/foo.js' ``` ## API ### resolveCwd(moduleId) Like `require()`, throws when the module can't be found. ### resolveCwd.silent(moduleId) Returns `null` instead of throwing when the module can't be found. #### moduleId Type: `string` What you would use in `require()`. ## Related - [resolve-from](https://github.com/sindresorhus/resolve-from) - Resolve the path of a module from a given path - [req-from](https://github.com/sindresorhus/req-from) - Require a module from a given path - [req-cwd](https://github.com/sindresorhus/req-cwd) - Require a module from the current working directory - [resolve-pkg](https://github.com/sindresorhus/resolve-pkg) - Resolve the path of a package regardless of it having an entry point - [lazy-req](https://github.com/sindresorhus/lazy-req) - Require modules lazily ## License MIT © [Sindre Sorhus](https://sindresorhus.com)