HTTP scatter.
Examples
Platform spec article
Examples
Spec standingStandard
-
pckgClient boundary
Context
Decision
HTTP via pckgClient.ts only.
Consequences
Shared auth.
Verification anchors
Grep fetch in packages/.
-
CLI for lock
Context
Lock integrity.
Decision
Use beskid fetch/lock via CLI.
Consequences
Shared resolver.
Verification anchors
Panel CLI invocations.
- Contracts and edge cases pckgClient HTTP rules, authentication, caching, and package command contracts.
- Decisions record (legacy index) Migration index for package manager panel ADRs.
- Design model PackageTreeItem sections, pckgClient surface, cache keys, and Packages view chrome.
- Examples Corelib locked dependencies and registry search in the Packages view.
- Flow and algorithm Package search, details expansion, fetch/lock, and focus-driven refresh sequences.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Purpose and scope
Section titled “Purpose and scope”Worked examples for local and registry sections of the package panel.
Corelib — This project
Section titled “Corelib — This project”Precondition: compiler/corelib open; member collections focused; Project.lock present.
Steps:
- Open Packages view.
- Expand This project.
Expected rows: Dependencies such as corelib with resolvedVersion from lock, registry: default, tooltip showing materialized path under .beskid/packages/.
Fetch/Lock: View title Lock runs beskid lock at packages/collections/; status bar shows lock phase; on success, locked versions refresh without restarting LSP.
Registry search — corelib
Section titled “Registry search — corelib”Precondition: Registry reachable at resolved base URL (workspace default or localhost).
Steps:
- View title Search → query
corelib. - Expand hit
corelib.
Expected: Versions list from PackageDetailsResponse.versions; latest non-yanked version highlighted; dependencies under expanded version match PackageDependencyResponse shapes.
Actions:
- Open in browser uses
buildRegistryPackageUrl. - Add dependency prompts version; after apply, user runs Fetch from view title.
Private registry with API key
Section titled “Private registry with API key”Precondition: Registry requires authentication; package my.internal.lib not visible anonymously.
Steps:
- Command palette → configure Beskid: Set Package Registry API Key (stores secret).
- Search
my.internal.lib.
Expected: Authenticated search returns hits; without key, 401 error node with configuration hint.