Prepare MessageCenter 0.1.0 - #1
Merged
Merged
Conversation
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
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.
Summary
Why
This consolidates the Pi-tested MessageCenter foundation into a standalone, hardware-independent 0.1.0 baseline. Compact and non-touch modes make MessageCenter a first-class MagicMirror module without requiring MMM-pages, Seymour, or a hardware adapter. Optional MQTT and local sockets let smart-home and system-monitoring producers use the same schema, while cached snapshots preserve the image associated with an event instead of showing a later camera frame.
Security and resource limits
Validation
npm test— 88 tests passingnpm audit --omit=dev --audit-level=high— zero vulnerabilitiesnpm pack --dry-run— successful with an isolated temporary npm cachegit diff --check— clean