performance-now
npmv2.1.0TypeScriptImplements performance.now (based on process.hrtime).
Not recommended for new projects
No — performance-now should not be adopted for new projects. Last published 3440 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 3440 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding performance-now to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the performance-now README.
var now = require("performance-now")
var start = now()
var end = now()
console.log(start.toFixed(3)) // the number of milliseconds the current node process is running
console.log((start-end).toFixed(3)) // ~ 0.002 on my systemDependencies
Declared by performance-now v2.1.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (7)
Used by
Popular packages that depend on performance-now.
Relationship graph
Dependencies (left) and dependents (right) of performance-now.
Frequently installed together
TypeScript definitions for node
resolve like require.resolve() on behalf of files asynchronously and synchronously
An AST-based pattern checker for JavaScript.
No description provided.
A high-level API to automate web browsers
Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
Bare bones Promises/A+ implementation
The semantic version parser used by npm.
BDD/TDD assertion library for node.js and the browser. Test framework agnostic.
Generates and consumes source maps
the most correct and second fastest glob implementation in JavaScript
An optimised way to copy'ing an object. A small and simple integration
Release history
No releases in the last two years, typically about 23 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.1.0latest | 9 years ago | — | MIT |
| 2.0.0 | 9 years ago | — | MIT |
| 1.0.2 | 9 years ago | — | MIT |
| 1.0.1 | 9 years ago | — | MIT |
| 1.0.0 | 9 years ago | — | MIT |
| 0.2.0 | 12 years ago | — | MIT |
| 0.1.4 | 12 years ago | — | MIT |
| 0.1.3 | 13 years ago | — | MIT |
| 0.1.2 | 13 years ago | — | MIT |
| 0.1.1 | 13 years ago | — | MIT |
| 0.1.0 | 13 years ago | — | MIT |
Overview
performance-now is an npm package that implements performance.now (based on process.hrtime). It has 2 known dependents in the graph. The latest version is 2.1.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need implements performance.now (based on process.hrtime) and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use performance-now?
No — performance-now should not be adopted for new projects. Last published 3440 days ago.
How do I install performance-now?
Run `npm install performance-now` to add performance-now to your npm project.
What license is performance-now released under?
performance-now is distributed under the MIT license.
How popular is performance-now?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on performance-now.
Is performance-now still maintained?
The most recent release of performance-now (v2.1.0) was published 9 years ago.
Does performance-now run install scripts?
No. performance-now does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.