rename moq-lite package to moq-net#1428
Merged
Merged
Conversation
The old name caused confusion because `moq-lite` is also the name of one of the wire protocols this library speaks. The new name reflects that this is the networking layer; at session setup it negotiates either the moq-lite or moq-transport wire protocol. - Rust: rs/moq-lite -> rs/moq-net (moq-net v0.1.0). rs/moq-lite kept as a thin shim that re-exports moq-net and will not receive further updates. - JS: js/lite -> js/net (@moq/net v0.1.0). @moq/lite kept as a shim that re-exports @moq/net with a runtime warning and JSDoc @deprecated. - Python: py/moq-lite -> py/moq-net (moq-net v0.1.0). py/moq-lite kept as a shim that re-exports moq_net and emits DeprecationWarning on import. All in-tree consumers (hang, moq-mux, moq-native, moq-relay, moq-ffi, libmoq, moq-cli, moq-clock, moq-boy, moq-gst, @moq/hang, @moq/watch, @moq/publish, etc.) now depend on moq-net / @moq/net. Protocol-level identifiers (ALPNs like `moq-lite-04`, the internal `lite/` submodule that implements the moq-lite protocol, spec URLs) are unchanged.
Reword the moq-net description across all surfaces to highlight what it actually provides: real-time pub/sub with built-in caching, fan-out, and prioritization, instead of the more abstract "networking layer" phrasing. Touches Cargo.toml/package.json/pyproject.toml descriptions, READMEs, lib.rs/__init__.py module docs, and the docs site.
The moq-lite Rust crate was renamed to moq-net, but doc/rs/ still linked to /rs/crate/moq-lite (which no longer exists), failing the VitePress build with 11 dead links. Update the affected pages and surrounding prose/snippets to reference moq-net. Wire-protocol references in doc/concept/ are intentionally left as moq-lite. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The old name caused confusion because
moq-liteis also the name of one of the wire protocols this library speaks. The new name reflects that this is the networking layer; at session setup it negotiates either the moq-lite or moq-transport wire protocol.All in-tree consumers (hang, moq-mux, moq-native, moq-relay, moq-ffi, libmoq, moq-cli, moq-clock, moq-boy, moq-gst, @moq/hang, @moq/watch, @moq/publish, etc.) now depend on moq-net / @moq/net.
Protocol-level identifiers (ALPNs like
moq-lite-04, the internallite/submodule that implements the moq-lite protocol, spec URLs) are unchanged.