@remits/remits-cli 0.1.120 → 0.1.121

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/package.json +1 -1
  2. package/skills/remits-cli/references/development-loop.md +2 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@remits/remits-cli",
3
- "version": "0.1.120",
3
+ "version": "0.1.121",
4
4
  "description": "Local CLI for auth, component sync, and live test execution against Remits",
5
5
  "license": "MIT",
6
6
  "private": false,
package/skills/remits-cli/references/development-loop.md CHANGED
@@ -321,7 +321,7 @@ If no relevant Test component exists yet, consider creating one. Test components
321
321
 
322
322
  New test files use the `new_` prefix (e.g., `new_MyTest.groovy`) and no `id:` in the sidecar — see "Creating a component that does not exist yet" in Step 2. Run them **by name** (`remits-cli test run --test "My Test"`) until a sync assigns an id and renames the file.
323
323
 
324
- **How to write the Test itself is not a CLI concern** — what a suite can assert, how mocks behave across HTTP/relay boundaries, driving an embeddable in-process, and the front-stage-only rule all live in `guides/components/test-components.md`. Read that before authoring a suite.
324
+ **How to write the Test itself is not a CLI concern** — what a suite can assert, how mocks behave across HTTP/relay boundaries, driving an embeddable in-process, and the front-stage-only rule all live in `guides/test-components.md`. Read that before authoring a suite.
325
325
 
326
326
  **Option B — Visual verification with Playwright** (for UI changes or when the user wants to "see it"):
327
327
 
@@ -362,7 +362,7 @@ They are not interchangeable. The loader's request carries **no path**, so it re
362
362
  purely from the embeddable-scoped token key's persisted context. The browser `tokenKey` names the account
363
363
  preview URL; `embedTokenKey` names the host-loader credential. The response also echoes `injectionType` /
364
364
  `renderMode` / `headMode`, which decide what a host actually receives
365
- (`guides/components/embeddable-components.md`).
365
+ (`guides/embeddable-components.md`).
366
366
 
367
367
  **This works for a `new_` component that has never been synced.** The embed token key carries the
368
368
  component NAME as well as its id, so a staged, id-less Embeddable is loader-addressable — you do not