</>PackageGraphPackageGraph

parse-node-version

npmv2.0.0

Turn node's process.version into something useful.

Not recommended for new projects

No — parse-node-version should not be adopted for new projects. Last published 1752 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1752 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 4.2 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 2 maintainers, and a contained dependency surface.

  • 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 parse-node-version to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

4.2 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >= 10.13.0
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the parse-node-version README.

var nodeVersion = require('parse-node-version')(process.version);

console.log(
  nodeVersion.major,
  nodeVersion.minor,
  nodeVersion.patch,
  nodeVersion.pre,
  nodeVersion.build
);

Dependencies

Declared by parse-node-version v2.0.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (6)

eslint ^7.32.0eslint-config-gulp ^5.0.1eslint-plugin-node ^11.1.0expect ^27.3.1mocha ^8.4.0nyc ^15.1.0

Used by

Popular packages that depend on parse-node-version.

Relationship graph

Dependencies (left) and dependents (right) of parse-node-version.

lessparse-node-version
parse-node-version dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 1028 days apart.

Recent versions of parse-node-version
VersionPublishedSizeLicense
2.0.0latest4 years ago4.2 KBMIT
1.0.17 years ago4.4 KBMIT
1.0.07 years ago4.0 KBMIT

Overview

parse-node-version is an npm package that turn node's process.version into something useful. It has 1 known dependents in the graph. The latest version is 2.0.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need turn node's process.version into something useful and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use parse-node-version?

No — parse-node-version should not be adopted for new projects. Last published 1752 days ago.

How do I install parse-node-version?

Run `npm install parse-node-version` to add parse-node-version to your npm project.

What license is parse-node-version released under?

parse-node-version is distributed under the MIT license.

How popular is parse-node-version?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on parse-node-version.

Is parse-node-version still maintained?

The most recent release of parse-node-version (v2.0.0) was published 4 years ago.

Does parse-node-version run install scripts?

No. parse-node-version does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.