@quatronic/qore 0.1.5 → 0.1.6

package/README.md

@@ -46,7 +46,26 @@ the portal. Working from a personal fork whose `origin` the portal doesn't
 know? As long as an `upstream` remote points at the real repository, that one
 resolves — the context line then says `(upstream)`.
 
-Pass `--module <slug|id>` to pick a module explicitly; the flag always wins
+Outside a repository, with a projects folder set (see `qore init`), the
+order is: the project you are standing in; else `[project]` /
+`--project <ref>` (`app`, `app/module`, `tenant/app` or `tenant/app/module`,
+matched against your local checkouts); else an interactive pick. `qore dev`
+takes the reference as an argument (`qore dev <app>`); `qore dev`, `qore env
+pull`, `qore run` and `qore status` take `--project`. `qore run --project`
+only chooses which module's secrets are used; the command still runs in the
+current directory. `qore env pull --project` writes into the located module,
+and a relative `--target` then resolves against that project directory, not
+the directory you ran it from.
+
+Logged out with a projects folder set, the local lookup still runs first: a
+folder that holds no projects gives `QORE_PROJECT_NOT_FOUND`; otherwise the
+project is located exactly as when logged in (a match, a picker, or
+`QORE_CONTEXT_REQUIRED` without a terminal), and the login error comes from
+the portal lookup that follows. Only without a projects folder does a logged-out
+command outside a project go straight to the login error.
+
+Pass `--module <slug|id>` to pick a module explicitly (it keeps its meaning and,
+like `--app`, still uses the portal lookup when you are not in a project); the flag always wins
 over the git remote. Inside a repository, `qore` still looks up the remote's
 own module (from the cache, or with one extra request) only so the context
 line can tell you when the flag overrides it. If a module is linked to more
@@ -92,7 +111,9 @@ qore env pull
 
 - The target file defaults to the module type's own convention (e.g.
   `.env.local`), or `.qore.json`'s `envFile`, or `--target <path>` — always
-  resolved against, and required to stay inside, the repository.
+  required to stay inside the repository. `envFile` resolves against the
+  repository root; `--target` against the current directory, or with
+  `--project` against the located project directory.
 - If the file doesn't exist yet, it's seeded from `.env.example` when one is
   present.
 - Existing values you've hand-edited are kept by default. A key the portal
@@ -301,6 +322,39 @@ If a repository resolves to no module on any portal you're logged in to,
 the error lists the portals it tried and, when a staging repository looks
 likely, suggests `qore login --portal staging`.
 
+### Projects folder & `qore init`
+
+`qore init` is the guided setup. It runs four steps and reports each as
+`done`, `already` or `skipped`, so running it again is safe:
+
+1. **Projects folder**: where your apps live (default `~/qore`; `--root <path>`
+   sets it without asking). Nothing existing is moved.
+2. **Login**: skipped when you are already logged in, and with `--no-input`.
+3. **Tenant**: `already` when a tenant is active (`done` right after the login
+   step logged you in). Otherwise skipped with
+   `--no-input` or when you are not logged in (run `qore tenant use <slug>`
+   later), skipped with no tenants, selected without a prompt when you have
+   one, a picker when you have several.
+4. **First app**: `--clone <app>` (with `--tenant <slug>` to disambiguate)
+   clones it; interactively it asks.
+
+With `--json`, stdout is one document: `{"projectsRoot": "<path>|null",
+"steps": {"root"|"login"|"tenant"|"clone": {"status", "detail?"}}}`.
+
+Apps clone into `<root>/<tenant>/<app>/<module>`. A checkout outside the
+folder registers itself the first time you use it (`qore clone <app> <dir>`,
+`qore dev`, ...); a registered checkout that was deleted is dropped. With a
+projects folder set, `qore dev`, `qore env pull`, `qore run` and `qore status`
+work from any directory (see Repository context).
+
+```sh
+qore config root              # show the folder and how many projects it holds
+qore config root <path>       # set it
+qore config root --unset      # clear it; known projects stay findable
+```
+
+`qore doctor` checks that the folder exists and is writable.
+
 ### Workspaces
 
 `qore clone` sets up a local directory holding one or more of an app's
@@ -319,6 +373,9 @@ qore sync                     # clone any module that's new, fetch the rest
 qore sync --pull              # ...and fast-forward every clean repository with an upstream
 ```
 
+- **Where it clones.** Without `[dir]` and with a projects folder set, `qore
+  clone` uses `<root>/<tenant>/<app>`. Without a projects folder it behaves as
+  described above and prints a tip to run `qore init`.
 - **`--protocol https|ssh`** picks the clone URL (default `https`). `ssh`
   rewrites `https://github.com/o/r` to `git@github.com:o/r.git`; your own
   git `insteadOf` config still applies on top of either.
@@ -485,8 +542,8 @@ qore whoami --json
 | Code | Meaning |
 |------|---------|
 | 0 | Success |
-| 1 | Internal error, `git` is not installed or not on `PATH`, the OS keychain is unavailable/access was denied, or qore itself needs a newer Node (`QORE_NODE_VERSION`, checked by `qore doctor`'s own `node` check against qore's own `process.version`); `qore dev`: its package manager isn't installed (`QORE_PACKAGE_MANAGER`), its install failed (`QORE_INSTALL_FAILED`), Docker is missing (`QORE_DOCKER_MISSING`), not running (`QORE_DOCKER_NOT_RUNNING`) or its compose v2 plugin is missing (`QORE_DOCKER_COMPOSE_MISSING`), a `db:up`/service failed, never became healthy (`QORE_SERVICE_UNHEALTHY`) or its data is incompatible (`QORE_SERVICE_DATA_INCOMPATIBLE`), or the repository's own `engines.node` doesn't match the `node` on `PATH` (`QORE_NODE_VERSION`, a different check from qore's own — `qore doctor`'s `node:<module>` check, run only in a trusted repository) |
-| 2 | Missing or invalid context (e.g. a bad `--portal` value, or no module selected), or the module is part of several apps and no `--app` was given; `qore dev`: a port is already in use (`QORE_PORT_IN_USE`) or the repository's dev setup isn't supported (`QORE_DEV_UNSUPPORTED`) |
+| 1 | Internal error, `git` is not installed or not on `PATH`, the OS keychain is unavailable/access was denied, or qore itself needs a newer Node (`QORE_NODE_VERSION`, checked by `qore doctor`'s own `node` check against qore's own `process.version`); `qore dev`: its package manager isn't installed (`QORE_PACKAGE_MANAGER`), its install failed (`QORE_INSTALL_FAILED`), Docker is missing (`QORE_DOCKER_MISSING`), not running (`QORE_DOCKER_NOT_RUNNING`) or its compose v2 plugin is missing (`QORE_DOCKER_COMPOSE_MISSING`), a `db:up`/service failed, never became healthy (`QORE_SERVICE_UNHEALTHY`) or its data is incompatible (`QORE_SERVICE_DATA_INCOMPATIBLE`), or the repository's own `engines.node` doesn't match the `node` on `PATH` (`QORE_NODE_VERSION`, a different check from qore's own — `qore doctor`'s `node:<module>` check, run only in a trusted repository); or the projects folder isn't writable (`QORE_ROOT_NOT_WRITABLE`, fix its permissions or choose another folder) |
+| 2 | Missing or invalid context (e.g. a bad `--portal` value, or no module selected), or the module is part of several apps and no `--app` was given; `qore dev`: a port is already in use (`QORE_PORT_IN_USE`) or the repository's dev setup isn't supported (`QORE_DEV_UNSUPPORTED`); projects folder: not set and not inside a project, for a logged-in user (`QORE_ROOT_NOT_SET`, run `qore init`; logged out with no folder you get the login error, exit 4, and logged out with a folder the local lookup runs first, so an empty folder still gives `QORE_PROJECT_NOT_FOUND`), not usable as a folder (`QORE_ROOT_INVALID`, pick another with `qore init --root <path>`), or no local project matches the reference or the folder holds none (`QORE_PROJECT_NOT_FOUND`, run `qore clone <app>`) |
 | 4 | Not logged in, session/login expired, login denied, or clock skew |
 | 5 | Access denied — lost tenant access, resource not found, no developer access |
 | 6 | Auth or API temporarily unreachable/unavailable |

package/dist/{chunk-QYBDINUC.js → chunk-OAU6HJHZ.js}

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 
-!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="a8210538-dc3e-507d-ab33-bdf6a49d6d16")}catch(e){}}();
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="885f6de1-0da7-54a5-86df-beaf550bdd8a")}catch(e){}}();
 import { createRequire as __qoreCreateRequire } from "node:module"; const require = __qoreCreateRequire(import.meta.url);
 
 // src/core/telemetry/scrub.ts
@@ -52,6 +52,21 @@ function replaceHome(s, ctx) {
   }
   return out;
 }
+var PKG = "node_modules/@quatronic/qore/";
+var NM = "node_modules/";
+function rewritePath(p, ctx) {
+  if (p.startsWith("app://") || !/^(?:file:\/\/|\/|[A-Za-z]:[\\/])/.test(p)) return { path: p };
+  let s = p.replace(/^file:\/\//, "");
+  if (ctx.platform === "win32") s = s.replace(/\\/g, "/").replace(/^\/(?=[A-Za-z]:)/, "");
+  const pkg = s.lastIndexOf(PKG);
+  const nm = s.lastIndexOf(NM);
+  if (pkg >= 0 && pkg === nm) return { path: `app:///${s.slice(pkg + PKG.length)}`, inApp: true };
+  if (nm >= 0) return { path: `app:///${s.slice(nm)}`, inApp: false };
+  return { path: `app:///${replaceHome(s, ctx).replace(/^\/+/, "")}` };
+}
+function framePath(p, ctx) {
+  return rewritePath(p, ctx).path;
+}
 function scrubText(s, ctx) {
   let out = s;
   for (const v of ctx.secretEnvValues) out = replaceLiteral(out, v, "[env]", "g");
@@ -83,8 +98,8 @@ function scrubBreadcrumb(b, ctx) {
   return { ...b, message: b.message === void 0 ? void 0 : scrubText(b.message, ctx), data: void 0 };
 }
 function scrubEvent(e, ctx) {
+  e.user = { ip_address: null };
   delete e.server_name;
-  delete e.user;
   delete e.request;
   delete e.extra;
   delete e.modules;
@@ -97,8 +112,12 @@ function scrubEvent(e, ctx) {
   for (const v of e.exception?.values ?? []) {
     if (v.value !== void 0) v.value = scrubText(v.value, ctx);
     for (const f of v.stacktrace?.frames ?? []) {
-      if (f.filename) f.filename = replaceHome(f.filename, ctx);
-      if (f.abs_path) f.abs_path = replaceHome(f.abs_path, ctx);
+      for (const k of ["filename", "abs_path"]) {
+        if (!f[k]) continue;
+        const r = rewritePath(f[k], ctx);
+        f[k] = r.path;
+        if (r.inApp !== void 0) f.in_app = r.inApp;
+      }
       if (f.module) f.module = replaceHome(f.module, ctx);
       delete f.vars;
       delete f.pre_context;
@@ -106,7 +125,7 @@ function scrubEvent(e, ctx) {
       delete f.post_context;
     }
   }
-  for (const img of e.debug_meta?.images ?? []) if (img.code_file) img.code_file = replaceHome(img.code_file, ctx);
+  for (const img of e.debug_meta?.images ?? []) if (img.code_file) img.code_file = framePath(img.code_file, ctx);
   if (e.breadcrumbs) e.breadcrumbs = e.breadcrumbs.map((b) => scrubBreadcrumb(b, ctx)).filter((b) => b !== null);
   return e;
 }
@@ -117,5 +136,5 @@ export {
   scrubBreadcrumb,
   scrubEvent
 };
-//# sourceMappingURL=chunk-QYBDINUC.js.map
-//# debugId=a8210538-dc3e-507d-ab33-bdf6a49d6d16
+//# sourceMappingURL=chunk-OAU6HJHZ.js.map
+//# debugId=885f6de1-0da7-54a5-86df-beaf550bdd8a