df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Resolved conflicts by taking GitHub versions for: - .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml Kept deploy.sh updated to: - Pull from GitHub (primary source) - Push to Gitea (push-mirror) - Build from site/ directory (GitHub structure) Co-Authored-By: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| index.js | ||
| license | ||
| package.json | ||
| readme.md | ||
resolve-from 
Resolve the path of a module like
require.resolve()but from a given path
Install
$ npm install resolve-from
Usage
const resolveFrom = require('resolve-from');
// There is a file at `./foo/bar.js`
resolveFrom('foo', './bar');
//=> '/Users/sindresorhus/dev/test/foo/bar.js'
API
resolveFrom(fromDir, moduleId)
Like require(), throws when the module can't be found.
resolveFrom.silent(fromDir, moduleId)
Returns null instead of throwing when the module can't be found.
fromDir
Type: string
Directory to resolve from.
moduleId
Type: string
What you would use in require().
Tip
Create a partial using a bound function if you want to resolve from the same fromDir multiple times:
const resolveFromFoo = resolveFrom.bind(null, 'foo');
resolveFromFoo('./bar');
resolveFromFoo('./baz');
Related
- resolve-cwd - Resolve the path of a module from the current working directory
- import-from - Import a module from a given path
- import-cwd - Import a module from the current working directory
- resolve-pkg - Resolve the path of a package regardless of it having an entry point
- import-lazy - Import a module lazily
- resolve-global - Resolve the path of a globally installed module
License
MIT © Sindre Sorhus