socket.io-parser
npmv4.2.7TypeScriptsocket.io protocol parser
Safe to adopt
Yes — socket.io-parser scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 56 days ago. 7 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 56 days ago. 7 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 3 transitive packages, about 132 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 socket.io-parser 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.
Licenses in the dependency tree
Every license you inherit by installing socket.io-parser, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=10.0.0
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the socket.io-parser README.
var parser = require('socket.io-parser');
var encoder = new parser.Encoder();
var packet = {
type: parser.EVENT,
data: 'test-packet',
id: 13
};
encoder.encode(packet, function(encodedPackets) {
var decoder = new parser.Decoder();
decoder.on('decoded', function(decodedPacket) {
// decodedPacket.type == parser.EVENT
// decodedPacket.data == 'test-packet'
// decodedPacket.id == 13
});Dependencies
Declared by socket.io-parser v4.2.7. Runtime dependencies are installed with the package; dev dependencies are not.
Used by
Popular packages that depend on socket.io-parser.
Relationship graph
Dependencies (left) and dependents (right) of socket.io-parser.
Frequently installed together
A light-weight module that brings Fetch API to node.js
An HTTP/1.1 client, written from scratch for Node.js
Promise based HTTP client for the browser and node.js
Fast, unopinionated, minimalist web framework
Next generation testing framework powered by Vite
HTTP and HTTPS modules that follow redirects.
node.js realtime framework server
Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. It includes many web standards from WHATWG DOM and HTML.
TypeScript definitions for node
Lightweight debugging utility for Node.js and the browser
A JavaScript implementation of many web standards
TypeScript definitions for ws
Release history
7 releases in the last two years, typically about 60 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.3.6 | 1 month ago | 17 KB | MIT |
| 3.4.5 | 1 month ago | 17 KB | MIT |
| 4.2.7latest | 1 month ago | 63 KB | MIT |
| 3.3.5 | 5 months ago | 18 KB | MIT |
| 3.4.4 | 5 months ago | 18 KB | MIT |
| 4.2.6 | 5 months ago | 63 KB | MIT |
| 4.2.5 | 8 months ago | 61 KB | MIT |
| 3.3.4 | 2 years ago | 17 KB | MIT |
| 4.2.4 | 3 years ago | 57 KB | MIT |
| 3.4.3 | 3 years ago | 17 KB | MIT |
| 4.2.3 | 3 years ago | 56 KB | MIT |
| 4.2.2 | 3 years ago | 52 KB | MIT |
| 3.3.3 | 3 years ago | 16 KB | MIT |
| 3.4.2 | 3 years ago | 17 KB | MIT |
| 4.0.5 | 4 years ago | 21 KB | MIT |
Overview
socket.io-parser is an npm package that socket.io protocol parser. It has 2 known dependents in the graph. The latest version is 4.2.7, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need socket.io protocol parser 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 (2 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 socket.io-parser?
Yes — socket.io-parser scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 56 days ago. 7 releases in the last 2 years.
How do I install socket.io-parser?
Run `npm install socket.io-parser` to add socket.io-parser to your npm project.
How many dependencies does socket.io-parser have?
socket.io-parser declares 2 direct dependencies and pulls in 3 packages in total once its runtime tree is resolved totalling about 132 KB on disk.
What license is socket.io-parser released under?
socket.io-parser is distributed under the MIT license.
How popular is socket.io-parser?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on socket.io-parser.
Is socket.io-parser still maintained?
The most recent release of socket.io-parser (v4.2.7) was published 1 month ago.
Does socket.io-parser run install scripts?
No. socket.io-parser does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.