chore(deps): interface deps as wide peer dependencies

[Upd4ting]

Move @antelopejs/interface-* from dependencies to peerDependencies with wide >= ranges. They are runtime singletons provided by the host, so peer ranges avoid dual installs and pinning overrides downstream. Verified: install (peers auto-installed), build, lint.

Greptile Summary

This PR moves @antelopejs/interface-api and @antelopejs/interface-core from dependencies to peerDependencies with wide >=0.0.3 <1.0.0 ranges, and mirrors them in devDependencies for local development. This is the correct pattern for runtime-singleton interface packages that are provided by the host application.

• package.json: Removes the dependencies block for both interface packages, adds them to peerDependencies with a wide >=0.0.3 <1.0.0 range, and mirrors them in devDependencies so the local build/test environment can still resolve them.
• pnpm-lock.yaml: Entries move from the dependencies section to devDependencies; both packages remain locked at 0.0.3, consistent with the new peer range floor.

Confidence Score: 5/5

Safe to merge — the restructuring correctly moves runtime-singleton interface packages to peer dependencies without altering any runtime logic.

The change is a pure dependency reorganization with no modifications to source code. Both packages are correctly declared in peerDependencies for consumers and mirrored in devDependencies for local development, which is the standard pattern. The lockfile resolves both packages to 0.0.3, matching the peer range floor.

No files require special attention.

Important Files Changed

Filename	Overview
package.json	Moves @antelopejs/interface-api and @antelopejs/interface-core from dependencies to peerDependencies (with wide >=0.0.3 <1.0.0 ranges) and adds them to devDependencies for local development — a correct pattern for runtime-singleton interface packages.
pnpm-lock.yaml	Reflects the package.json restructuring — entries moved from dependencies to devDependencies section; both packages locked to 0.0.3 (unchanged), consistent with the new peer range floor.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Consumer project"] -->|"installs"| B["@antelopejs/interface-api-util"]
    A -->|"must provide (peerDep) >=0.0.3 <1.0.0"| C["@antelopejs/interface-api"]
    A -->|"must provide (peerDep) >=0.0.3 <1.0.0"| D["@antelopejs/interface-core"]
    B -->|"devDependency (local dev/test)"| C
    B -->|"devDependency (local dev/test)"| D
    C -->|"runtime singleton"| D

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["Consumer project"] -->|"installs"| B["@antelopejs/interface-api-util"]
    A -->|"must provide (peerDep) >=0.0.3 <1.0.0"| C["@antelopejs/interface-api"]
    A -->|"must provide (peerDep) >=0.0.3 <1.0.0"| D["@antelopejs/interface-core"]
    B -->|"devDependency (local dev/test)"| C
    B -->|"devDependency (local dev/test)"| D
    C -->|"runtime singleton"| D

Loading

_{Reviews (2): Last reviewed commit: "chore(deps): interface deps as bounded p..." | Re-trigger Greptile}

[greptile-apps]

Dual install of interface-core persists despite stated goal

The PR description says this change avoids dual installs, but the lockfile still contains two copies of @antelopejs/interface-core: 0.0.3 pulled in transitively by @antelopejs/interface-api@0.0.4, and 0.0.5 resolved for the root peer dep. Because these packages act as runtime singletons, having two distinct module instances loaded at once can cause interface identity checks to silently fail (e.g., instanceof guards or symbol-keyed registries). The dual install will persist until @antelopejs/interface-api itself also declares @antelopejs/interface-core as a peer dependency rather than a regular one.

Prompt To Fix With AI

This is a comment left during a code review.
Path: pnpm-lock.yaml
Line: 45-49

Comment:
**Dual install of `interface-core` persists despite stated goal**

The PR description says this change avoids dual installs, but the lockfile still contains two copies of `@antelopejs/interface-core`: `0.0.3` pulled in transitively by `@antelopejs/interface-api@0.0.4`, and `0.0.5` resolved for the root peer dep. Because these packages act as runtime singletons, having two distinct module instances loaded at once can cause interface identity checks to silently fail (e.g., `instanceof` guards or symbol-keyed registries). The dual install will persist until `@antelopejs/interface-api` itself also declares `@antelopejs/interface-core` as a peer dependency rather than a regular one.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

The peer range floor for @antelopejs/interface-api is bumped from 0.0.3 (the previously declared minimum) to 0.0.4, and @antelopejs/interface-core is bumped from 0.0.3 to 0.0.5. If there is no API break between those versions that this package depends on, the narrower floor unnecessarily breaks consumers who are still on 0.0.3. The PR description frames this as a pure organizational change ("avoid dual installs"), so the rationale for the higher floor should be documented. If 0.0.3 is still compatible, consider lowering the floor back to >=0.0.3.

Suggested change

	"peerDependencies": {
	"@antelopejs/interface-api": ">=0.0.4",
	"@antelopejs/interface-core": ">=0.0.5"
	}
	"peerDependencies": {
	"@antelopejs/interface-api": ">=0.0.3",
	"@antelopejs/interface-core": ">=0.0.3"
	}

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 53-56

Comment:
The peer range floor for `@antelopejs/interface-api` is bumped from `0.0.3` (the previously declared minimum) to `0.0.4`, and `@antelopejs/interface-core` is bumped from `0.0.3` to `0.0.5`. If there is no API break between those versions that this package depends on, the narrower floor unnecessarily breaks consumers who are still on `0.0.3`. The PR description frames this as a pure organizational change ("avoid dual installs"), so the rationale for the higher floor should be documented. If `0.0.3` is still compatible, consider lowering the floor back to `>=0.0.3`.

```suggestion
  "peerDependencies": {
    "@antelopejs/interface-api": ">=0.0.3",
    "@antelopejs/interface-core": ">=0.0.3"
  }
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[Upd4ting]

@greptileai review