</>PackageGraphPackageGraph

engine.io-parser

npmv5.2.3TypeScript

Parser for the client for the realtime Engine

Adopt with care

engine.io-parser is usable, with caveats. Last published 790 days ago.

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

    No download data reported for this package yet.

  • DMaintenance: grade D, Poor — a real concern.

    Last published 790 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 45 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 engine.io-parser 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.

45 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.0.0
Module format
ESM + CommonJS
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the engine.io-parser README.

const parser = require("engine.io-parser");
const data = Buffer.from([ 1, 2, 3, 4 ]);

parser.encodePacket({ type: "message", data }, encoded => {
  const decodedData = parser.decodePacket(encoded); // decodedData === data
});

Dependencies

Declared by engine.io-parser v5.2.3. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on engine.io-parser.

Relationship graph

Dependencies (left) and dependents (right) of engine.io-parser.

@mswjs/intercepto…engine.ioengine.io-parser
engine.io-parser dependencies dependents

Frequently installed together

Release history

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

Recent versions of engine.io-parser
VersionPublishedSizeLicense
5.2.3latest2 years ago45 KBMIT
5.2.22 years ago45 KBMIT
5.2.13 years ago45 KBMIT
5.2.03 years ago41 KBMIT
5.1.03 years ago36 KBMIT
5.0.73 years ago30 KBMIT
5.0.63 years ago28 KBMIT
5.0.53 years ago28 KBMIT
5.0.44 years ago28 KBMIT
5.0.34 years ago24 KBMIT
5.0.24 years ago29 KBMIT
5.0.14 years ago28 KBMIT
5.0.05 years ago28 KBMIT
4.0.35 years ago17 KBMIT
4.0.25 years ago17 KBMIT

Overview

engine.io-parser is an npm package that parser for the client for the realtime Engine. It has 2 known dependents in the graph. The latest version is 5.2.3, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need parser for the client for the realtime Engine 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).
  • Lean dependency tree (1 direct dependencies).

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 engine.io-parser?

engine.io-parser is usable, with caveats. Last published 790 days ago.

How do I install engine.io-parser?

Run `npm install engine.io-parser` to add engine.io-parser to your npm project.

What license is engine.io-parser released under?

engine.io-parser is distributed under the MIT license.

How popular is engine.io-parser?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on engine.io-parser.

Is engine.io-parser still maintained?

The most recent release of engine.io-parser (v5.2.3) was published 2 years ago.

Does engine.io-parser run install scripts?

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