npm

js-message

3.1.1RIAEvangelist/js-message ↗New releases in your daily digest, changelog included.

A tiny, normalized JavaScript and JSON message envelope for every runtime boundary

Last release 20 days ago
24 Aug 2026
Ships fairly regularly
a new release about every 2.9 years
Some releases are documented
notes for 6 of 11 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
11 releases · first in 2015

Release timeline

11 releases since 2015

2015201720192021

Releases

3.1.124 Aug 2026
[Roshi's Codex PRIME] Native browser conformance patch: bare-package imports now run through explicit native import maps, the shared Node/Chrome inven
[Roshi's Codex PRIME] Native browser conformance patch: bare-package imports now run through explicit native import maps, the shared Node/Chrome inventory includes an observable no-build behavioral journey, packed-consumer metadata and dependency-tree gates protect the zero-runtime-dependency boundary, and the recovery playground path is proven in real Chrome.
Open source →
Additional notes2 sources agree
Added

A seven-scenario Behavioral suite for request/reply, object-transport, payload-free signal, diagnostic, long-lived receiver, cross-entry consumer, and native no-bundler journeys.

Native Chrome evidence that the shared suite and playground resolve the bare js-message package import through explicit checked-in import maps.

Packed-consumer metadata and dependency-tree assertions plus production and full npm audits in CI.

Changed

js-message works with bundlers and without a bundler. Bundlers resolve the bare package import normally; native browser ESM uses a standard import map with no build or transpilation step. Browser-facing documentation now provides the complete map, HTTP(S) serving requirements, and the unsupported file:// boundary.

Static documentation and deployment checks now protect import-map ordering, package mappings, CSP authorization, and the package's zero-runtime-dependency contract.

Fixed

The recovery playground recipe now sends genuinely malformed JSON and is executed in real Chrome to prove the observable error envelope and subsequent recovery.
Open source →

3.1.022 Aug 2026

Restores optional type and data fields without dummy payloads or error envelopes.

[Roshi's Codex PRIME]

Highlights

Restores optional type and data fields without dummy payloads or error envelopes.
Supports native ESM and synchronous CommonJS from the same source on Node.js 22.13+.
Improves direct-object loading to about 257 million operations per second in the recorded benchmark, with reproducible results and accessible charts.
Adds focused Why, Performance, playground, recipe, and testing documentation pages.
Expands verification to 76 nonduplicated shared checks, 11 real-Chrome playground checks, exact packed-artifact tests, and 100% Node/Chrome coverage.

Migration note

The minimum supported Node.js version is now 22.13.0. See MIGRATION.md for the complete 3.1 upgrade guidance.

Open source →

Additional notes2 sources agree

Added

An editable, time-limited GitHub Pages playground using the canonical checked-in module, with focused recipe pages and real-Chrome integration coverage.
Unit, Functional, Integration, and Regression vanilla-test catalogs with unique case IDs and per-suite commands.
Synchronous CommonJS loading from the same native ES-module source used by import.
Reproducible 3.0-versus-3.1 benchmarks, accessible charts, recorded results, and focused Performance and Why pages.

Changed

The Node.js runtime floor is now 22.13.0, where synchronous require(ESM) no longer emits an experimental warning by default.
Shared runtime requirements are divided into 76 smaller nonduplicated checks, plus eleven distinct Chrome-only playground checks.
Packed-artifact verification now enforces the exact npm file set.
Loading uses assignment semantics instead of a duplicate schema-validation pass, improving direct-object throughput while preserving native JSON behavior.

Fixed

Messages may once again omit type, data, or both; missing fields remain undefined instead of becoming error envelopes.

Open source →

3.0.016 Aug 2026

3.0.0 publishes the modernized js-message package as a supported npm and GitHub release.

Highlights

Added a canonical package entry with matching default and named Message exports.
Constructors and load() now accept JSON text or existing { type, data } envelopes.
Added toJSON() for structured-clone transports and predictable JSON.stringify() output.
Aligned the browser-global build with the ES-module implementation through globalThis.Message.
Added a shared vanilla-test protocol suite for Node and Chrome with 100% native coverage.
Added compatibility checks across Node.js 13.2 through 24, package-artifact verification, and documentation/server tests.
Published focused multi-page documentation, migration guidance, examples, and a new repository header.

Breaking changes

Inputs must now be non-array objects with their own type and data properties; invalid shapes produce an error envelope instead of silently assigning undefined.
Browser-global JSON and load are now non-enumerable prototype members.
The package now exposes an explicit, curated export and file surface; unsupported internal deep paths are no longer shipped.

Compatibility retained

Root default imports and the established Message.js and js-message-vanilla.js paths remain supported.
Mutable, enumerable type and data, the JSON getter, and load() returning undefined are preserved.
Buffer, boxed-string, typed-view, and custom JSON-coercible inputs remain accepted.
The package remains dependency-free at runtime and retains its Node.js >=13.2.0 engine floor.

See the migration guide for details.

npm install [email protected]

Artifact SHA-256: 19DF4AEFDDB7F0E82FC80EB178AED565D2472AD6FA2BF1096252DB892683BA82

Open source →

Additional notes2 sources agree

Added

A canonical index.js entry with matching default and named Message exports.
Constructor and load() support for existing { type, data } objects.
Compatibility parsing for Buffer, boxed strings, typed views, and other JSON-coercible text inputs accepted by earlier releases.
A public toJSON() method for structured-clone transports and native JSON.stringify integration.
A shared vanilla-test protocol suite for Node and real-browser coverage.
Package compatibility, documentation, local-link, and packed-artifact verification.
Focused, accessible GitHub Pages documentation for getting started, API, protocol, browsers, examples, testing, and migration.
A generated three-to-one repository header and social preview.

Changed

Valid JSON values without own type and data keys now become error envelopes instead of silently producing undefined fields.
The legacy browser-global implementation now matches the ES-module contract and targets globalThis.
Package metadata uses an explicit file allowlist and supported export map while preserving both legacy deep paths.
Local documentation serving no longer needs node-http-server.

Fixed

Serialized parse and validation errors now retain stable name and message fields when the preserved response is JSON-safe.
The package lock metadata, scripts, homepage, description, and dependency classification now match package.json.
Browser examples use valid closing script tags and standard WebSocket event APIs.

Open source →