pi-chrome 0.4.0 → 0.4.1

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.
Files changed (2) hide show
  1. package/README.md +1 -1
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -29,7 +29,7 @@ pi install ./pi-chrome
29
29
 
30
30
  ### Why an unpacked Chrome extension?
31
31
 
32
- The Chrome Web Store does not allow extensions that talk to a local bridge controlled by another tool, so `pi-chrome` ships its companion as an unpacked extension you load yourself. The source is small, MIT-licensed, and lives in `extensions/chrome-profile-bridge/browser-extension/` next to this README — read it before loading.
32
+ `pi-chrome` cannot ship through the Chrome Web Store: a Web Store extension is not allowed to talk to a local bridge controlled by another tool. Instead it ships as a small, MIT-licensed unpacked extension in `extensions/chrome-profile-bridge/browser-extension/` — read the source before loading. `/chrome-doctor` reports the loaded extension version and warns when it drifts from the installed `pi-chrome`.
33
33
 
34
34
  ## First-time setup
35
35
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "pi-chrome",
3
- "version": "0.4.0",
4
- "description": "Control your existing authenticated Chrome profile from Pi with tabs, snapshots, clicks, typing, JS evaluation, waits, and screenshots \u2014 background by default.",
3
+ "version": "0.4.1",
4
+ "description": "Drive your existing logged-in Chrome from Pi \u2014 no re-login, no throwaway profile, background by default.",
5
5
  "keywords": [
6
6
  "pi-package",
7
7
  "pi-extension",