revyse 0.1.0 → 0.2.0

package/README.md

@@ -5,14 +5,15 @@ your running dev server, say what should change, review the diff and the checks,
 revert.
 
 ```bash
-npx revyse init    # detect the project, accept the data disclosure, add withRevyse() to next.config
-npx revyse login   # link this machine to your Revyse project
-npx revyse dev     # run the local agent next to your dev server; the overlay appears in the app
+npx revyse init    # set up: the disclosure, next.config, the packages, the project on Revyse
+npm run dev        # your dev server as usual: Revyse starts with it and the overlay appears
 ```
 
-`npx revyse init` installs nothing by itself: add `@revyse/next` to your dev dependencies
-(`npm i -D @revyse/next`). The browser check needs Chromium (`npx playwright install
-chromium`) or Chrome; without it the check reports "not run".
+`init` installs `revyse` and `@revyse/next` as dev dependencies and opens the browser to
+create (or pick) the project on Revyse. `@revyse/next` starts the local agent inside `next
+dev`, so there is nothing else to run. `npx revyse login` connects to another project later,
+and `npx revyse dev` runs the agent on its own, for dev servers `withRevyse()` doesn't wrap. The browser check needs Chromium (`npx
+playwright install chromium`) or Chrome; without it the check reports "not run".
 
 How Revyse handles your code: https://revyse.dev/data-handling
 

package/dist/agent.js

@@ -0,0 +1,11 @@
+#!/usr/bin/env node
+import {
+  identifyAgent,
+  loadConfig,
+  startLocalAgent
+} from "./chunk-FYWZYXR4.js";
+export {
+  identifyAgent,
+  loadConfig,
+  startLocalAgent
+};