Package Exports
- has-require
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 (has-require) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
has-require 
Check if code requires any module or a specific id
Installing
$ npm install --save has-requireUsage
var hasRequire = require('has-require')
hasRequire('require("foo")', 'foo') // => true
hasRequire.any('require') // => falseAPI
For full implementation details, see the Checker API.
hasRequire(code, id) -> boolean
code
Required
Type: string
The code to check.
id
Required
Type: string
The module id to check, e.g. 'http'.
hasRequire.any(code) -> boolean
code
Required
Type: string
The code to check.
Checker
new hasRequire.Checker(code) -> checker
code
Required
Type: string
The code to store on the checker.
checker.any() -> boolean
Checks if any string literal is required. The result is cached. The following code won't be matched:
requirerequire()require('')
checker.has(id) -> boolean
id
Required
Type: string
The module id to check, e.g. 'http'.
Uses checker.any() first, so calling has for multiple ids when no require is present (!checker.any()) will avoid needlessly re-testing the code.
License
MIT © Ben Drucker