</>PackageGraphPackageGraph

sync-message-port

npmv1.2.0TypeScript

A Node.js communication port that can pass messages synchronously between workers

Safe to adopt

Yes — sync-message-port scores well across adoption, maintenance, weight, supply chain, and licensing. 4.8M downloads per week and 1 known dependents. Last published 224 days ago. 6 releases in the last 2 years.

  • AAdoption: grade A, Excellent.

    4.8M downloads per week and 1 known dependents.

  • BMaintenance: grade B, Good.

    Last published 224 days ago. 6 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 105 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • 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 sync-message-port 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.

105 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 >=16.0.0
Module format
CommonJS only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the sync-message-port README.

jsFull README ↗
import {Worker} from 'node:worker_threads';
import {SyncMessagePort} from 'sync-message-port';
// or
// const {SyncMessagePort} = require('sync-message-port');

// Channels must be created using this function. A MessageChannel created by
// hand won't work.
const channel = SyncMessagePort.createChannel();
const localPort = new SyncMessagePort(channel.port1);

const worker = new Worker(`
  import {workerData} from 'node:worker_threads';
  import {SyncMessagePort} from 'sync-message-port';
Example truncated — see the full README.

Dependencies

Declared by sync-message-port v1.2.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (10)

@types/jest ^30.0.0@types/node ^25.0.3gts ^7.0.0jest ^30.0.3minipass 7.1.2npm-run-all ^4.1.5ts-jest ^29.0.5ts-node ^10.2.1typedoc ^0.28.0typescript ^5.0.2

Used by

Popular packages that depend on sync-message-port.

sync-child-processnpm

Run a subprocess synchronously and interactively in Node.js

↓ 0/wk◈ 1 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of sync-message-port.

sync-child-processsync-message-port
sync-message-port dependencies dependents

Frequently installed together

ts-nodenpm

TypeScript execution environment and REPL for node.js, with source map support

↓ 42.2M/wk◈ 38 dependents⚖ MITTS
jestnpm

Delightful JavaScript Testing.

↓ 42.1M/wk◈ 70 dependents⚖ MITTS
@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS

Release history

1 release in the last two years, typically about 3 days apart.

Recent versions of sync-message-port
VersionPublishedSizeLicense
1.2.0latest7 months ago105 KBMIT
1.1.31 year ago59 KBMIT
1.1.21 year ago58 KBMIT
1.1.11 year ago58 KBMIT
1.1.01 year ago7.3 KBMIT
1.0.01 year ago54 KBMIT

Overview

sync-message-port is an npm package that a Node.js communication port that can pass messages synchronously between workers. It is very popular, with about 4.8M downloads per week and 1 known dependents in the graph. The latest version is 1.2.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need a Node.js communication port that can pass messages synchronously between workers and value a battle-tested, widely-adopted 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

  • Large, well-established user base (4.8M weekly downloads).
  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • No significant drawbacks detected from available metadata.

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

Maintainers

nex3

Frequently asked questions

Should I use sync-message-port?

Yes — sync-message-port scores well across adoption, maintenance, weight, supply chain, and licensing. 4.8M downloads per week and 1 known dependents. Last published 224 days ago. 6 releases in the last 2 years.

How do I install sync-message-port?

Run `npm install sync-message-port` to add sync-message-port to your npm project.

What license is sync-message-port released under?

sync-message-port is distributed under the MIT license.

How popular is sync-message-port?

sync-message-port has approximately 4,828,340 downloads per week and 1 known dependent packages.

Is sync-message-port still maintained?

The most recent release of sync-message-port (v1.2.0) was published 7 months ago.

Does sync-message-port run install scripts?

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