npm‑registry‑package‑info is a Node.js library (and CLI) that fetches metadata for one or many npm packages from a registry, returning a summary of successful lookups and any failures. It’s aimed at developers or scripts that need to programmatically query the npm registry (or a custom one) for package details such as versions, dependencies, etc.
Total donated
Undistributed
Share with your subscribers:
Recipients
How the donated funds are distributed
Support the dependencies of kgryte/npm-registry-package-info
Lightweight debugging utility for Node.js and the browser
parse argument options
Wraps JSON#parse in a try/catch block.
Merge and extend objects.
Validates if a value is a boolean primitive.
Validates if a value is a function.
Validates if a value is a nonnegative integer.
Validates if a value is a JavaScript object.
Validates if a value is a string primitive.
Validates if a value is an array of string primitives.
Function which does nothing.
browser-side require() the node way
BDD/TDD assertion library for node.js and the browser. Test framework agnostic.
lcov posting to codecov.io
Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use ca
Static analysis tool for JavaScript
List an author's packages.
Proxies nodejs require in order to allow overriding dependencies during testing.
Proxyquire in Node and Proxyquireify in the browser with no code changes
Proxies browserify's require in order to allow overriding dependencies during testing.
Formatted TAP output like Mocha's spec reporter
tap-producing test harness for node and browsers
write tests for browser code
Support the repos that depend on this repository
Top contributors
kgryte
16 contributions
Recent events
Kivach works on the Obyte network, and therefore you can track all donations.
No events yet