npmpackage.info

Gathering detailed insights and metrics for browserify-require-not-found-parent

browserify-require-not-found-parent

Report pathname of parent module when resolving require() fails in Browserify.

0.1.0

MIT

JavaScript

108,171 3

Installations

npm install browserify-require-not-found-parent

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

1

Total

1

Closed

0

Releases

Unable to fetch releases

Developer

jmm

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

5.4.1

NPM Version

3.6.0 Statistics

3 Commits

2 Watching

1 Branches

1 Contributors

Updated on 05 Feb 2016

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

108,171

Last day

-46.7%

104

Compared to previous day

Last week

-20%

642

Compared to previous week

Last month

3,021

Compared to previous month

Last year

122.9%

31,739

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

browserify mocha sinon

Versions

When resolving a require() fails with MODULE_NOT_FOUND (Error: Cannot find module 'dep' from 'parent'), report the requiring module's pathname instead of just its directory.

Installation:

browserify-require-not-found-parent on npm.

Usage:

1var browserifyRequireNotFoundParent =
2  require("browserify-require-not-found-parent");
3
4browserify()
5.plugin(browserifyRequireNotFoundParent)

See:

https://github.com/substack/node-resolve/pull/64

https://github.com/substack/node-browserify/issues/1083

https://github.com/substack/node-browserify/issues/1117

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

SAST

Determines if the project uses static code analysis.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

Score

3

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More