npmpackage.info

Gathering detailed insights and metrics for browser-process-hrtime

browser-process-hrtime

⌚ Browser shim for Node.js process.hrtime()

1.0.0

BSD-2-Clause

JavaScript

3,163,911,231 3.2

Installations

npm install browser-process-hrtime

Pull Requests

Open

2

Total

5

Closed

0

Merged

3

Issues

Open

2

Total

7

Closed

5

Releases

Unable to fetch releases

Developer

kumavis

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

8.11.3

NPM Version

6.3.0 Statistics

25 Stars

23 Commits

8 Forks

1 Watching

2 Branches

4 Contributors

Updated on 25 Oct 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

3,163,911,231

Last day

-30.3%

1,823,747

Compared to previous day

Last week

-6.1%

14,209,240

Compared to previous week

Last month

34.3%

55,646,920

Compared to previous month

Last year

-20.2%

533,158,573

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

No dependencies detected.

Versions

browser-process-hrtime

Browser shim for Node.js process.hrtime(). See documentation at nodejs.org

This module does not provide the same level of time precision as node.js, but provides a matching API and response format.

usage

Use hrtime independent of environment (node or browser). It will use process.hrtime first and fallback if not present.

1const hrtime = require('browser-process-hrtime')
2const start = hrtime()
3// ...
4const delta = hrtime(start)

monkey-patching

You can monkey-patch process.hrtime for your dependency graph like this:

1process.hrtime = require('browser-process-hrtime')
2const coolTool = require('module-that-uses-hrtime-somewhere-in-its-depths')

note

This was originally pull-requested against node-process, but they are trying to stay lean.

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.

1

Code-Review

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

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.

0

SAST

Determines if the project uses static code analysis.

Score

3.2

/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