@swmansion/argent 0.30.2-next.13 → 0.30.2-next.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli-cmds.mjs +22 -6
- package/dist/client.js +21 -5
- package/dist/installer.mjs +2 -1
- package/dist/mcp-server.mjs +31 -8
- package/dist/tool-server.cjs +292 -50
- package/package.json +1 -1
- package/skills/argent-native-profiler/SKILL.md +1 -0
- package/skills/argent-react-native-profiler/SKILL.md +2 -0
package/package.json
CHANGED
|
@@ -57,6 +57,7 @@ You do not need to derive `app_process` manually; just make sure the app is laun
|
|
|
57
57
|
|
|
58
58
|
Call `native-profiler-start` with `device_id` (iOS UDID or Android serial). The tool auto-detects the running app and saves the trace to `/tmp/argent-profiler-cwd/` with a timestamped filename.
|
|
59
59
|
Let the user interact with the app or drive interaction via simulator tools (see `argent-device-interact` skill).
|
|
60
|
+
While a profiler records, interaction tools return no automatic screenshot or element tree, so the capture does not load the app. Call `screenshot` or `describe` when you need to see the screen; interaction tools still wait for the screen to settle before they return, so add no wait of your own; on an Android emulator each screenshot during a profile takes one frame in about 100 ms and does not wake the screen capture; on a physical Android device it takes about 150–200 ms and briefly wakes the device screen capture, so take them sparingly there.
|
|
60
61
|
|
|
61
62
|
### Step 2: Stop and export
|
|
62
63
|
|
|
@@ -88,6 +88,8 @@ Mind the react-native and ios-native profiler selection mentioned above when sta
|
|
|
88
88
|
- if session is marked as "stale", you may overtake it without prompting the user for allowance
|
|
89
89
|
- if session is NOT "stale" - before taking action and terminating the other session, **stop and ask user what you should do**, explaining the situation.
|
|
90
90
|
|
|
91
|
+
While a profiler records, interaction tools return no automatic screenshot or element tree, so the capture does not load the app. Call `screenshot` or `describe` when you need to see the screen; interaction tools still wait for the screen to settle before they return, so add no wait of your own; on an Android emulator each screenshot during a profile takes one frame in about 100 ms and does not wake the screen capture; on a physical Android device it takes about 150–200 ms and briefly wakes the device screen capture, so take them sparingly there.
|
|
92
|
+
|
|
91
93
|
#### Annotate every interaction
|
|
92
94
|
|
|
93
95
|
After each `gesture-tap` or `gesture-swipe` call, record an annotation using the returned `timestampMs`. Compute `offsetMs = timestampMs - startedAtEpochMs`. Do this for _every_ interaction, including back-navigation swipes, not just the primary action. Pass all collected annotations to `react-profiler-analyze` in Step 3.
|