</>PackageGraphPackageGraph

bytes

npmv3.1.2

Utility to parse a string bytes to bytes and vice-versa

Not recommended for new projects

No — bytes should not be adopted for new projects. Last published 1686 days ago.

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

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1686 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 12 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 bytes 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.

12 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 >= 0.8
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the bytes README.

var bytes = require('bytes');

bytes vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
bytesthis page03MIT4 years ago
color-convert299.6M1MIT1 day ago
set-cookie-parser50.2M2MIT1 day ago
meow36.7M1MIT1 day ago
rgb2hex01MIT1 day ago
strnum01MIT1 day ago

Dependencies

Declared by bytes v3.1.2. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (4)

eslint 7.32.0eslint-plugin-markdown 2.2.1mocha 9.2.0nyc 15.1.0

Used by

Popular packages that depend on bytes.

Relationship graph

Dependencies (left) and dependents (right) of bytes.

raw-bodybody-parser@adobe/css-toolsbytes
bytes dependencies dependents

Frequently installed together

Release history

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

Recent versions of bytes
VersionPublishedSizeLicense
3.1.2latest4 years ago12 KBMIT
3.1.14 years ago12 KBMIT
3.1.07 years ago11 KBMIT
3.0.09 years agoMIT
2.5.09 years agoMIT
2.4.010 years agoMIT
2.3.010 years agoMIT
2.2.010 years agoMIT
2.1.011 years agoMIT
2.0.211 years agoMIT
2.0.111 years agoMIT
2.0.011 years agoMIT
1.0.012 years agoMIT
0.3.012 years agoMIT
0.2.113 years agoMIT

Overview

bytes is an npm package that utility to parse a string bytes to bytes and vice-versa. It has 3 known dependents in the graph. The latest version is 3.1.2, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need utility to parse a string bytes to bytes and vice-versa 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 bytes?

No — bytes should not be adopted for new projects. Last published 1686 days ago.

How do I install bytes?

Run `npm install bytes` to add bytes to your npm project.

What license is bytes released under?

bytes is distributed under the MIT license.

How popular is bytes?

npm does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on bytes.

Is bytes still maintained?

The most recent release of bytes (v3.1.2) was published 4 years ago.

Does bytes run install scripts?

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