@swmansion/argent 0.32.1-next.13 → 0.32.1-next.14

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@swmansion/argent",
3
- "version": "0.32.1-next.13",
3
+ "version": "0.32.1-next.14",
4
4
  "mcpName": "io.github.software-mansion/argent",
5
5
  "description": "MCP server for iOS Simulator and Android Emulator control",
6
6
  "license": "Apache-2.0",
@@ -13,7 +13,7 @@ Physical iPhone: not supported; `react-profiler-*` reject `kind: "device"`. Prof
13
13
 
14
14
  - `react-profiler-start` / `react-profiler-stop`: record CPU samples and React commits around an interaction.
15
15
  - `react-profiler-analyze`: turn the recording into a ranked report: hot commits with the JS functions that ran during each.
16
- - `react-profiler-status`: **only after an interruption** (debugger drop, Metro reload, pause, subagent handoff, any doubt), never otherwise. A debugger drop also ends the recording; check status before stopping or restarting.
16
+ - `react-profiler-status`: **only after an interruption** (debugger drop, Metro reload, pause, subagent handoff, any doubt), never otherwise. After a debugger drop, react-profiler-stop can no longer collect the run; check status before stopping or restarting.
17
17
  - `react-profiler-component-source`: source, location and memoization status of a component the report flagged.
18
18
  - `react-profiler-renders`: how many instances of each component are mounted in the top 30 levels of the tree, with their last render time; no session needed. It does not count re-renders: record a profile for that.
19
19
  - `react-profiler-fiber-tree`: live component hierarchy, no session needed, for tracing a component's ancestry.
@@ -98,7 +98,7 @@ If the user does not want changes, present the report and suggest the fix withou
98
98
 
99
99
  ## 4. Caveats
100
100
 
101
- - **Dev builds** render ~3x slower than production (the report notes it). Prioritize render counts over durations: counts carry over to production. They are already halved when Strict Mode double-invokes renders.
101
+ - **Dev builds** render ~3x slower than production (the report notes it). Prioritize render counts over durations: counts carry over to production. Strict Mode can double durations, but not counts.
102
102
  - **Live API data** may differ between runs (payload sizes, item counts) and shift render counts and durations independently of your fix. Note when data-dependent components vary.
103
103
  - **Run-to-run noise:** variations under ~10-15% in commit duration may be noise; only treat consistent, directional changes as signal.
104
104
  - **Profiler overhead:** if the native profile shows `JSLexer`, `JSONEmitter` or Hermes internals dominating the JS thread, that is instrumentation cost, not app work. Discount those entries.