@withbuddi/buddi 0.1.0-pre.37 → 0.1.0-pre.39

package/node_modules/real-require/README.md

@@ -1,5 +1,9 @@
 # real-require
 
+[![Package Version](https://img.shields.io/npm/v/real-require.svg)](https://npm.im/real-require)
+[![Dependency Status](https://img.shields.io/librariesio/release/npm/real-require)](https://libraries.io/npm/real-require)
+[![Build](https://github.com/pinojs/real-require/workflows/CI/badge.svg)](https://github.com/pinojs/real-require/actions?query=workflow%3ACI)
+
 Keep require and import consistent after bundling or transpiling.
 
 ## Installation
@@ -12,13 +16,9 @@ npm install real-require
 
 ## Usage
 
-The package provides two drop-ins functions, `realRequire` and `realImport`,
-which can be used in scenarios where tools like transpilers or bundlers change
-the native `require` or `await import` calls.
+The package provides two drop-ins functions, `realRequire` and `realImport`, which can be used in scenarios where tools like transpilers or bundlers change the native `require` or `await import` calls.
 
-The current `realRequire` functions only handles webpack at the moment, wrapping
-the `__non_webpack__require__` implementation that webpack provides for the
-final bundle.
+The current `realRequire` functions only handles webpack at the moment, wrapping the `__non_webpack__require__` implementation that webpack provides for the final bundle.
 
 ### Example
 

package/node_modules/real-require/package.json

@@ -1,6 +1,6 @@
 {
   "name": "real-require",
-  "version": "1.0.0",
+  "version": "0.2.0",
   "description": "Keep require and import consistent after bundling or transpiling",
   "author": "Paolo Insogna <shogun@cowtech.it>",
   "homepage": "https://github.com/pinojs/real-require",
@@ -23,16 +23,27 @@
     "src"
   ],
   "scripts": {
-    "lint": "eslint .",
-    "lint:fix": "eslint --fix .",
-    "test": "c8 --reporter=text --reporter=html borp 'test/*.test.js'",
-    "test:ci": "c8 --reporter=text --reporter=json --check-coverage --branches 90 --functions 90 --lines 90 --statements 90 borp 'test/*.test.js'",
-    "ci": "npm run lint && npm run test:ci"
+    "format": "prettier -w src test",
+    "lint": "eslint src test",
+    "test": "c8 --reporter=text --reporter=html tap --reporter=spec --no-coverage test/*.test.js",
+    "test:watch": "tap --watch --reporter=spec --no-browser --coverage-report=text --coverage-report=html test/*.test.js",
+    "test:ci": "c8 --reporter=text --reporter=json --check-coverage --branches 90 --functions 90 --lines 90 --statements 90 tap --no-color --no-coverage test/*.test.js",
+    "ci": "npm run lint && npm run test:ci",
+    "prepublishOnly": "npm run ci",
+    "postpublish": "git push origin && git push origin -f --tags"
   },
   "devDependencies": {
-    "borp": "^1.0.0",
-    "c8": "^8.0.0",
-    "eslint": "^9.39.4",
-    "neostandard": "^0.13.0"
+    "eslint": "^7.12.0",
+    "eslint-config-standard": "^16.0.3",
+    "eslint-plugin-import": "^2.25.2",
+    "eslint-plugin-node": "^11.1.0",
+    "eslint-plugin-promise": "^5.1.1",
+    "eslint-plugin-standard": "^5.0.0",
+    "c8": "^7.10.0",
+    "prettier": "^2.4.1",
+    "tap": "^16.0.0"
+  },
+  "engines": {
+    "node": ">= 12.13.0"
   }
 }

package/node_modules/real-require/src/index.js

@@ -1,9 +1,9 @@
-/* eslint-disable no-new-func */
+/* eslint-disable no-new-func, camelcase */
 /* globals __non_webpack__require__ */
 
 const realImport = new Function('modulePath', 'return import(modulePath)')
 
-function realRequire (modulePath) {
+function realRequire(modulePath) {
   if (typeof __non_webpack__require__ === 'function') {
     return __non_webpack__require__(modulePath)
   }

package/node_modules/thread-stream/node_modules/real-require/LICENSE.md

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2021 Paolo Insogna and the real-require contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/node_modules/thread-stream/node_modules/real-require/README.md

@@ -0,0 +1,51 @@
+# real-require
+
+Keep require and import consistent after bundling or transpiling.
+
+## Installation
+
+Just run:
+
+```bash
+npm install real-require
+```
+
+## Usage
+
+The package provides two drop-ins functions, `realRequire` and `realImport`,
+which can be used in scenarios where tools like transpilers or bundlers change
+the native `require` or `await import` calls.
+
+The current `realRequire` functions only handles webpack at the moment, wrapping
+the `__non_webpack__require__` implementation that webpack provides for the
+final bundle.
+
+### Example
+
+```js
+// After bundling, real-require will be embedded in the bundle
+const { realImport, realRequire } = require('real-require')
+
+/*
+  By using realRequire, at build time the module will not be embedded and at runtime it will try to load path from the local filesytem.
+  This is useful in situations where the build tool does not support skipping modules to embed.
+*/
+const { join } = realRequire('path')
+
+async function main() {
+  // Similarly, this make sure the import call is not modified by the build tools
+  const localFunction = await realImport('./source.js')
+
+  localFunction()
+}
+
+main().catch(console.error)
+```
+
+## Contributing
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md)
+
+## License
+
+Copyright Paolo Insogna and real-require contributors 2021. Licensed under the [MIT License](http://www.apache.org/licenses/MIT).

package/node_modules/thread-stream/node_modules/real-require/package.json

@@ -0,0 +1,38 @@
+{
+  "name": "real-require",
+  "version": "1.0.0",
+  "description": "Keep require and import consistent after bundling or transpiling",
+  "author": "Paolo Insogna <shogun@cowtech.it>",
+  "homepage": "https://github.com/pinojs/real-require",
+  "contributors": [
+    {
+      "name": "Paolo Insogna",
+      "url": "https://github.com/ShogunPanda"
+    }
+  ],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/pinojs/real-require.git"
+  },
+  "bugs": {
+    "url": "https://github.com/pinojs/real-require/issues"
+  },
+  "main": "src/index.js",
+  "files": [
+    "src"
+  ],
+  "scripts": {
+    "lint": "eslint .",
+    "lint:fix": "eslint --fix .",
+    "test": "c8 --reporter=text --reporter=html borp 'test/*.test.js'",
+    "test:ci": "c8 --reporter=text --reporter=json --check-coverage --branches 90 --functions 90 --lines 90 --statements 90 borp 'test/*.test.js'",
+    "ci": "npm run lint && npm run test:ci"
+  },
+  "devDependencies": {
+    "borp": "^1.0.0",
+    "c8": "^8.0.0",
+    "eslint": "^9.39.4",
+    "neostandard": "^0.13.0"
+  }
+}

package/node_modules/thread-stream/node_modules/real-require/src/index.js

@@ -0,0 +1,14 @@
+/* eslint-disable no-new-func */
+/* globals __non_webpack__require__ */
+
+const realImport = new Function('modulePath', 'return import(modulePath)')
+
+function realRequire (modulePath) {
+  if (typeof __non_webpack__require__ === 'function') {
+    return __non_webpack__require__(modulePath)
+  }
+
+  return require(modulePath)
+}
+
+module.exports = { realImport, realRequire }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withbuddi/buddi",
-  "version": "0.1.0-pre.37",
+  "version": "0.1.0-pre.39",
   "type": "module",
   "description": "Your personal agents, on your computer",
   "repository": {
@@ -17,7 +17,7 @@
     "buddi": "packages/install/dist/launcher.js"
   },
   "buddi": {
-    "notes": "### Added\n\n- Knowing you: Settings → Profile takes your full name, pronouns and birthday (day and month, the year optional) beside what the agents call you, and every agent is told them — and that today is your birthday when it is. On the day your front desk greets you first thing in your zone with a short note from the team, on Telegram and on Home under \"Happy birthday\", with a picture from your Illustrator when the image plugin has an account (on by default; the switch is on Missions).\n- People: the people in your life are their own kind of memory — who they are to you, how to address them, birthdays and anniversaries, a few notes — read by every agent in one line each and edited in Settings → Memory → People, with Forget and Undo. An agent keeps someone at once only when you told it about them in that message; otherwise you get a card to keep or discard. The people your existing notes already name are offered once, the same way. A person with a date can remind you a week before and on the day, with an offer to find something (off until you turn it on in their sheet).\n- The front desk and the Chief of Staff's morning brief read all-day \"Happy birthday!\", \"Anniversary\" and \"Marion's birthday\" events as occasions and say them in words, never as events with a time.\n- Agents decide when there is only one option and ask with buttons when there are a few: with one calendar they may change (or one mailbox, one account) they use it and say which; with two to six they ask with choices you tap in the chat, the corner chat or Telegram, never in prose; and they state the defaults they chose, such as two hours for a dinner, on the confirmation or the approval card. A question may now offer six choices.\n\n- Plugins can sign you in to an account with OAuth, starting with Google (host API 1.28): buddi opens Google's consent, catches the answer on this computer (or takes the address you paste back when your browser is on another one), keeps the tokens in Keys and secrets, renews them itself and sends them only to Google's API for that plugin. The plugin never sees a token; a sign-in Google stops accepting is reported as such.\n- Plugin pages can draw a choice per row (a segment such as Not linked · Read · Read and change, an option greyed with why), a grouped list whose heads carry the group's own actions, a row's colour as a dot, one button that opens a short menu of actions and forms, a card that finishes by itself once what it waits for arrives, and parts shown only when the dashboard is opened on this computer or only from elsewhere (host API 1.28). Settings → Calendar is the first page to use them.\n- A plugin's calendar page can open an event in a sheet on the right — when and how long, its calendar and colour, the place as a map link, the notes, a link to it in Google Calendar or iCloud — with Move or change… and Cancel…, which open the corner chat with the request written in for you to send; and it can say how many events the week holds beside its dates (host API 1.28).\n- Skills can be bundles: upload a `.zip` holding a SKILL.md with its scripts and assets (Agents → Skills → Upload). buddi checks it before keeping anything — 20 MB and 500 files at most, no paths that climb out, no links, nothing that runs outside `scripts/` — and shows what is inside, then the row says BUNDLE and who can run its scripts, and its sheet shows the files as a tree you can read (only SKILL.md is editable; Download gives the .zip back). Nothing in a bundle runs on upload. A script runs only when an agent holding host.exec runs it, never while the bundle is untrusted, asking you every time on a card that names the script, the bundle, the arguments, the working folder and what it may touch (Allow once only); it is confined (the macOS sandbox or bubblewrap on Linux): it writes only in its own folder, reads only the bundle, that folder and the system it runs on (nothing in your home), and has no network unless the bundle's SKILL.md says `network: true`, which its card then says. A shipped example, `examples/skills/letterhead`, shows a template bundle with no scripts.\n- The chat's composer styles what you type as you type it, and what is sent is the same plain Markdown: code and fenced blocks tinted with the block's language, bold, italic, headings, links and list markers. `@` in any chat offers who you can name with their faces (Agent Father borrowed for one message, or a teammate the agent asks for you; a group's members in a group) and draws the name as a chip; `/` at the start offers /use, /new, /stop and /quiet, then commands plugins add in their manifest (`commands`); lists carry on with Enter and indent with Tab; pasted code is fenced with Undo, and a paste over 4,000 characters becomes a file at once with \"Put it in the message\". On a phone the lists sit above the keyboard.\n\n- Agents try before they decline: every agent is told to look with the browser when it has one (your own browser where you are signed in, or buddi's with a login you stored in Keys and secrets, asking you to take over at a code it cannot answer), to hand a colleague's question to that colleague and relay the answer, and only then to say exactly what it lacks with one next step. An agent without the browser says it could look if you gave it browser control.\n- Catalogue agents can be given the browser's stored logins (`secret.list`, `secret.fill`) and colleagues to hand work to: a package's `delegates` resolve at install to the agents you have, an agent added later joins the lists that name it and the front desk's, and the approval card says who may ask whom.\n\n- A first run with no key at all: the **Ollama on this computer** card shows the command that installs Ollama (Homebrew or the app on a Mac, the official script on Linux; buddi never runs it), notices when Ollama starts, fetches the model your machine's memory suits (`qwen3:1.7b` to `qwen3:14b`) with a progress bar, makes the Ollama account and puts your assistant on it, so it answers before first run ends. It says plainly that a small local model is slower and weaker than Claude or ChatGPT, offers Ollama Cloud on a machine that would be slow, and Home's tip offers a stronger brain while any agent thinks with the local model.\n- `buddi doctor` has an `ollama` row: running with its version and models and which accounts use it, or a warning when an account uses it and Ollama is stopped or the account's model is not fetched.\n\n- Widgets in the market: Browse has a **Widgets** shelf beside All · Plugins · Agents with every widget a listed plugin brings, drawn as Home draws it from the plugin's sample data, and a listing's sheet shows each widget at every size it offers; Home's Add widgets and the lock screen's Add a widget end with **Get more widgets**. A plugin declares the sample as `preview` on a widget (one body, or one per size), `buddi plugins describe` now reports each widget (id, title, sizes, settings, preview) for the market's check, and a plugin that is only a widget is welcome.\n- A news edition in chat is drawn as an edition card: its name and time, the voice note as a waveform, its first sentence, each topic with its stories (the outlet's logo, the headline with Update or Opinion, Anchor's line, the outlet linked out and \"and N more\"), and the next edition's time. The text as sent is one tap away under \"Show as text\", and is what shows when News cannot read the edition back.\n\n- `pnpm review` for working on buddi: Codex reviews everything since the last release tag (from the Unreleased lines and a standard focus list) into a file, the script prints the brief for a second review agent, and `--merge` puts both reviews into one findings file.\n\n- Each story in a news edition card has its ways out under ⋯, as on the News page: Not interested, Mute an outlet, Quiet the topic for a week, Mute the topic. The story leaves a sentence and Undo in its place.\n\n### Changed\n\n…"
+    "notes": "- Logins: signing in again with a new password on a site where buddi keeps your login asks \"Update the login for amazon.com?\"; Update replaces the password it keeps. Signing in with the password it already keeps asks nothing, also after a restart and in your Chrome (a login saved before this release is asked about once). Saving two accounts on one site at once keeps both.\n- Logins: Save says \"Saved\" for two seconds once the login is really kept, or why it couldn't be kept with Try again — in the Page tab and in your Chrome's bar. In your Chrome the question survives the sign-in page moving on (a redirect to another page of the same site asks again there), and a Save pressed just after Give it back still counts.\n- Missions: a mission asks you one question at a time; asking the same unanswered question again within a day doesn't interrupt you (it leaves one quiet line under Needs you), and the \"needed you\" line for the same question is sent once a day at most.\n- Missions: when a mission running while you're away gets stuck, it asks you once on Telegram (with its choices as buttons) and carries on with your answer, instead of ending without a word; no answer within the wait (an hour by default) and you get one line saying it needed you.\n- buddi.app for Mac: an app that runs buddi with nothing to install, now a real app window with menus: the dashboard in its own window (first run and the lock screen included), a dock icon, the standard macOS menu bar (New Conversation, Settings, Lock, Find, Zoom, Check for Updates), microphone, downloads and native notifications, and the menu-bar glyph for status; first build, not yet distributed.\n- Logins: when you take over a page and sign in, buddi offers to keep that login for next time — \"Save this login for amazon.com?\" with Save, Not now and Never for this site, above the page in the Page tab, or in the \"buddi is waiting\" bar in your Chrome. Save keeps it under Settings → Keys and secrets (\"Login · amazon.com · for sam@… · saved 3 Oct\", with Remove), and agents sign in there with it without ever seeing the password; no agent, chat or log sees it. Your Chrome needs the extension from this release.\n- buddi.app for Mac: buddi updates itself from inside the app (Settings → System or \"Update to …\" in the menu): the new version is checked against npm's integrity hash and its signed provenance, tested, and only then switched to, with the version before kept; Advanced → Restart with the Previous Version goes back to it. Each release now builds a signed, notarized DMG for withbuddi.com once the signing keys are in place.\n- Chat: the round Send button is back at the right of the composer when Use my Chrome sits beside the model and Thinking; in a narrow box (the corner chat, a squeezed column) the model chip steps aside and the chip says just \"Chrome\".\n- Your Chrome: a page opens in an ordinary Chrome window, in the background, even when the window you last used is a popup or an installed app; when Chrome won't group the tab there, the page still opens (the \"buddi\" group is skipped), and with no ordinary window it opens in a new one that doesn't take the focus, with one line in the chat saying so.\n- Your Chrome: when the page opened and a later step failed, the agent gets the page and \"opened, then this failed\" instead of \"I couldn't open it\"; the same failure twice in a row is said plainly once rather than tried a third time.\n- Page tab: the page sits in a small browser window, with back, forward, reload and the address on a bar above it. While the agent drives, the bar is there but asleep and a click on the address copies it; a thin line along the bar shows a page loading.\n- Page tab: while you have the page in buddi's browser, back, forward and reload work, and you can type an address and press Enter to go there (the same sites the agent may visit; file and internal addresses are refused). The address follows the links you click.\n- Page tab: an Enlarge button beside Stop / Take over (and \"Open the full page view\" under ⋯) opens the page over the whole window with the same header; Esc or the button brings it back.\n- Page tab: the Keyboard button only shows on a phone, where it says \"Type into the page\"; on a computer, click the page and type.\n- Page tab: your pointer on the page is an arrow, not a crosshair.\n- Page tab: after reloading the dashboard while you have the page, clicks and typing reach it again straight away, without pressing Drive it here (on a computer; a phone still asks).\n- Your Chrome: Take over on a page in your Chrome brings its tab to the front of Chrome instead of waiting for a picture that never came; the bar in the tab says \"buddi is waiting\" with Give it back, and Give it back there or in the Canvas lets the agent carry on in that tab. Needs the extension from this release.\n- Your Chrome: when you asked for your Chrome (the Use my Chrome pin, the agent's setting, or the task) and buddi couldn't use it, the reply says why in one line: not connected to this buddi, not open right now, or turned off for agents in Settings.\n- A page that shows up signed out where the task needs your account (an Amazon cart saying \"Sign in to your account\") now asks with the \"needs your sign-in\" card, or moves to your Chrome where you're signed in, instead of the agent asking you in chat; a news front page with a Sign in link is left alone. Google's sign-in page under the title \"Gmail\" is now recognised as a sign-in page too.\n- Agents answer a list of items from a website (a cart, orders, search results) as a short list, one line per item, instead of a wide table; a table only when you ask for a comparison.\n- Lock screen: the widgets keep refreshing while it's locked, even in a tab in the back, and catch up the moment you look at it again; a slow answer can no longer put older headlines back over newer ones.\n- Settings → System: a version npm has just published but isn't serving yet is no longer offered; the panel says \"npm is still processing 0.1.0-pre.N; try again in a few minutes\" with no Upgrade button, and an upgrade that still runs into npm's 404 for buddi's own tarball says that same sentence instead of npm's output. A registry or mirror that needs your npm credentials (it gets the ones in your ~/.npmrc) or refuses the check is never mistaken for one still processing, and any other npm failure is shown in npm's own words, with credentials masked.\n- Cloudflare setup: after \"Remove what buddi made\", the panel says your Cloudflare API token is still kept here and still valid in Cloudflare, with a \"Forget the token\" button and where to revoke it (My Profile → API Tokens); Remove no longer drops the token on its own, so setting it up again doesn't ask for it. From the terminal: `buddi access cloudflare forget-token`."
   },
   "files": [
     "packages",