Package Exports
- require-resolve
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (require-resolve) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
require-resolve
Use the node way to resolve required path to absolute path.
Install
$ npm install --save require-resolveUsage
var requireResolve = require('../'),
path = require('path');
// Resolve a absolute file
console.log(requireResolve(__filename));
// Resolve a relative file
console.log(requireResolve('./example/simple.js', path.dirname(path.dirname(__filename))));
// output:
/*
{
src: '/Users/{your_name}/Workspace/require-resolve/example/simple.js',
pkg: {
name: 'require-resolve',
version: '0.0.1',
main: 'src/require-resolve.js',
root: '/Users/{your_name}/Workspace/require-resolve'
}
}
*/
// Resolve a node module file
console.log(requireResolve('glup', __filename));
console.log(requireResolve('glup/taskTree', __filename));Contributing
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using gulp.
License
Copyright (c) 2015 Zhonglei Qiu. Licensed under the MIT license.