PROD-58888: bump jarvis-emitter ^1→^3.0.2 and meaco ^1.0→^1.1.0 - #10
Draft
greg3d wants to merge 2 commits into
Draft
PROD-58888: bump jarvis-emitter ^1→^3.0.2 and meaco ^1.0→^1.1.0#10greg3d wants to merge 2 commits into
greg3d wants to merge 2 commits into
Conversation
Skipping two majors of jarvis-emitter (^1.0.0 → ^3.0.2) and one of meaco (^1.0.0 → ^1.1.0). The runtime API surface used here — `new JarvisEmitter()`, `interfaceProperty()` builder, `extend([...])`, `JarvisEmitter.role.event`, shorthand `.callX()`/`.X()` accessors — is unchanged across versions. No source code changes required. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates libijs’s runtime dependencies to align with the org-wide jarvis-emitter@3.x upgrade and to consume meaco@1.1.0, aiming to avoid multiple hoisted copies when used alongside the gen3 framework.
Changes:
- Bump
jarvis-emitterfrom^1.0.0to^3.0.2. - Bump
meacofrom^1.0.0to^1.1.0.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
meaco@2.1.x moves jarvis-emitter to a shared ^3.0.2 dep so it dedupes with libijs's direct dep — the prior ^1.1.0 pin was never published and would not resolve. 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
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
jarvis-emitter^1.0.0→^3.0.2(skips two majors)meaco^1.0.0→^1.1.0Why — PROD-58888
libijs was the last consumer still pulling a v1 of jarvis-emitter. Aligning it with the org-wide v3 upgrade and the new
meaco@1.1.0keeps a single hoisted copy of jarvis-emitter when this lib is consumed alongside the gen3 framework.Compatibility check
Audited every JarvisEmitter usage in
lib/,tools/,examples/. The patterns used here are unchanged from v1 → v3 at runtime:new JarvisEmitter()(no-arg constructor)JarvisEmitter.interfaceProperty().name(...).role(...).sticky(...).description(...).build()— builder API unchangedthis.extend([...])— array form accepted at runtime in all versionsJarvisEmitter.role.event— same string value"event"in v3.callX()/.X()accessors — still auto-generated in v3 for non-reserved names"obsereve"typo (now"observe"in v3) anywhere in the treeMerge / release order
This PR is #4 of 5 for PROD-58888. Merge alongside aura-agent after meaco@1.1.0 is published.
meaco@1.1.0Test plan
npm installresolves a singlejarvis-emitter@3.x(no nested duplicates)examples/script (e.g.afc.js) against an attached iOS devicetools/backupandtools/appscommands