@buoy-gg/js-top 7.0.36 → 7.0.38

package/README.md

@@ -10,7 +10,7 @@
 
 ---
 
-Every React Native developer has watched JS FPS tank and asked: **what is using it all?** JS Top answers live:
+JS Top ranks measured callback time. For example, a task table might look like this (illustrative values):
 
 ```
 #  TASK ORIGIN                        5S MS   %BUSY  CALLS  AVG   MAX
@@ -21,17 +21,35 @@ Every React Native developer has watched JS FPS tank and asked: **what is using
 ```
 
 - **Pure JavaScript.** No native module, no debugger, no dev client — works in **Expo Go** and even release builds.
-- **Zero overhead when closed.** The engine only runs while the tool is open (or a Buoy Desktop dashboard is watching).
-- **Honest accounting.** Exclusive-time bookkeeping (nested callbacks never double-count), a calibrated busy probe for true thread occupancy, and an explicit *unattributed* row for work no JS wrapper can see.
+- **Capture lifecycle.** The engine only runs while the tool is open (or a Buoy Desktop dashboard is watching).
+- **Honest accounting.** Exclusive-time bookkeeping (nested callbacks never double-count), a calibrated probe that estimates thread occupancy, and an explicit *unattributed* row for work no JS wrapper can see.
 - **Blocking-task attribution.** Every 50ms+ freeze (via React Native's `longtask` observer) is matched to the callback that overlapped it.
 
 ## Install
 
 ```bash
-npm install @buoy-gg/js-top
+npm install @buoy-gg/core @buoy-gg/js-top
 ```
 
-With Buoy auto-discovery, that's it — JS TOP appears in your floating menu. Explicit registration:
+## Before you start
+
+Use a development build with `@buoy-gg/core` and a Free or Pro Buoy account key. From your app’s directory, sign in:
+
+```bash
+npx --package=@buoy-gg/core buoy login
+```
+
+For Expo, initialize Buoy before rendering the menu:
+
+```tsx
+import { Buoy } from "@buoy-gg/core";
+
+Buoy.init({ licenseKey: process.env.EXPO_PUBLIC_BUOY_KEY });
+```
+
+The login command writes the Expo key to `.env.local`. For React Native CLI, pass the key from your app’s environment configuration; React Native does not load `.env.local` automatically. Mount `FloatingDevTools` inside the same providers as your screens and restart the development server after installation. The [Quick Start](https://buoy.gg/buoy/latest/docs/quick-start) shows the complete root component setup.
+
+After setup, open JS Top, run a known timer-driven interaction, and inspect the task table. Explicit registration:
 
 ```tsx
 import { FloatingDevTools } from "@buoy-gg/core";
@@ -42,15 +60,23 @@ import { jsTopPreset, jsTopModalPreset } from "@buoy-gg/js-top";
 
 ## How it works
 
-You can't sample a blocked JS thread from JS — so JS Top doesn't sample. It wraps every entry point work can take onto the thread (`setTimeout` / `setInterval` / `setImmediate` / `requestAnimationFrame` / `queueMicrotask` / Promise reactions / legacy-bridge call-ins) and deterministically times each callback, attributing cost to **where the callback was scheduled from** — with lazy stack capture so hot origins get named `setInterval ← startPolling` without per-call overhead.
+You can't sample a blocked JS thread from JS — so JS Top doesn't sample. It wraps supported scheduling entry points (`setTimeout` / `setInterval` / `setImmediate` / `requestAnimationFrame` / `queueMicrotask` / Promise reactions / legacy-bridge call-ins) and deterministically times each callback, attributing cost to **where the callback was scheduled from** — with lazy stack capture so hot origins get named `setInterval ← startPolling` while limiting stack-capture work.
+
+On the New Architecture, touch/React-commit work enters through paths pure JS can't wrap; that time shows as *unattributed* (the in-tool banner explains). Work outside wrapped paths, including some async/await continuations and native entry points, can remain unattributed.
 
-On the New Architecture, touch/React-commit work enters through paths pure JS can't wrap; that time shows as *unattributed* (the in-tool banner explains). Timers, rAF, microtasks and Promise chains are always fully attributed.
+## Desktop & AI
 
-## Buoy Desktop + AI
+To connect a React Native app to [Buoy Desktop](https://github.com/Buoy-gg/Buoy-Desktop) or MCP, install `@buoy-gg/external-sync` and follow the [Desktop connection guide](https://buoy.gg/buoy/latest/docs/desktop). Sign in to Desktop separately. [MCP setup](https://buoy.gg/buoy/latest/docs/mcp) also requires a process account and Pro access. Available remote actions depend on the tool and app integration.
+
+## Remote capabilities
 
 - The desktop dashboard mirrors the device's task table live, and adds a dev-only **per-function Hermes sampler** (attaches to Metro's inspector).
 - Via the Buoy MCP server, your AI agent can call `get_js_thread_top` — "why is JS FPS low?" becomes one tool call.
 
+## Account and plan requirements
+
+Use a Free or Pro Buoy account. History limits and paid features vary by tool; see [pricing](https://buoy.gg/pricing). Production access requires Pro where supported. Development-only hooks and actions remain unavailable in release builds.
+
 ## License
 
 Part of [React Buoy](https://buoy.gg). See buoy.gg for licensing.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@buoy-gg/js-top",
-  "version": "7.0.36",
-  "description": "Live Task Manager for the React Native JS thread — see which timers, Promises, and callbacks are eating your JS FPS, ranked in real time. Part of Buoy devtools.",
+  "version": "7.0.38",
+  "description": "Inspect instrumented JavaScript timers, promises and callbacks to investigate work on the React Native JS thread.",
   "main": "lib/commonjs/index.js",
   "module": "lib/module/index.js",
   "types": "lib/typescript/index.d.ts",
@@ -12,7 +12,7 @@
   ],
   "sideEffects": false,
   "dependencies": {
-    "@buoy-gg/shared-ui": "^7.0.36"
+    "@buoy-gg/shared-ui": "^7.0.38"
   },
   "peerDependencies": {
     "react": "*",