blob: 7f36e02963c68dfd490a27f82c3294c4f6098144 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
# resolve-cwd [](https://travis-ci.org/sindresorhus/resolve-cwd)
> Resolve the path of a module like [`require.resolve()`](http://nodejs.org/api/globals.html#globals_require_resolve) but from the current working directory
Unlike `require.resolve()` it returns `null` instead of throwing when the module can't be found.
## 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)
#### 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
- [lazy-req](https://github.com/sindresorhus/lazy-req) - Require modules lazily
## License
MIT © [Sindre Sorhus](http://sindresorhus.com)
|
