chore(deps): interface-core as bounded peer + dev dependency

[Upd4ting]

Move @antelopejs/interface-core from dependencies to peerDependencies (bounded to the current major, e.g. >=0.0.5 <0.1.0) and mirror it in devDependencies for standalone compilation. interface-core is a host-provided runtime singleton; this avoids dual installs and version-pinning overrides downstream. Verified: install, build, lint.

Greptile Summary

This PR moves @antelopejs/interface-core from dependencies to peerDependencies (with a mirrored entry in devDependencies), correctly treating it as a host-provided singleton to avoid duplicate installs and downstream version-pinning conflicts.

• @antelopejs/interface-core is removed from runtime dependencies and added to both peerDependencies and devDependencies with the range >=0.0.3 <1.0.0, allowing the dev environment to build and the consuming host to supply the package.
• The pnpm lockfile is updated accordingly, resolving the dev copy to 0.0.3.

Confidence Score: 5/5

Safe to merge — the dependency restructuring is mechanically correct, and the dev and peer ranges are now consistent with each other.

The change correctly removes interface-core from runtime dependencies and places it in both peerDependencies and devDependencies with matching ranges. The only open question is whether the upper bound should be <0.1.0 rather than <1.0.0, since the PR description's example suggested a tighter bound — but this is a minor design choice, not a defect in the restructuring itself.

package.json — worth confirming the intended upper bound of the peer range (<0.1.0 vs <1.0.0).

Important Files Changed

Filename	Overview
package.json	Moves @antelopejs/interface-core from dependencies to peerDependencies + devDependencies; both use the same range (>=0.0.3 <1.0.0). The range is broader than the PR description's example (which suggested <0.1.0), spanning all 0.x versions where minor bumps can be breaking.
pnpm-lock.yaml	Lockfile updated to reflect the move: interface-core removed from runtime dependencies, added under devDependencies resolving to 0.0.3. No issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[interface-rethinkdb] --> B[peerDependencies: interface-core >=0.0.3 <1.0.0]
    A --> C[devDependencies: interface-core >=0.0.3 <1.0.0]
    A --> D[dependencies: rethinkdb-ts ^2.7.0]
    E[Downstream consumer app] --> F[installs interface-core as host singleton]
    E --> G[installs interface-rethinkdb]
    G --> B
    F -. satisfies peer .-> B

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[interface-rethinkdb] --> B[peerDependencies: interface-core >=0.0.3 <1.0.0]
    A --> C[devDependencies: interface-core >=0.0.3 <1.0.0]
    A --> D[dependencies: rethinkdb-ts ^2.7.0]
    E[Downstream consumer app] --> F[installs interface-core as host singleton]
    E --> G[installs interface-rethinkdb]
    G --> B
    F -. satisfies peer .-> B

Loading

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

[greptile-apps]

The ^0.0.5 specifier in devDependencies does not mirror the peer range. For 0.0.x versions, npm/pnpm treats the caret as a patch-level pin (>=0.0.5 <0.0.6), meaning the dev install is locked to exactly 0.0.5 while the peer range allows any 0.0.x up to 0.1.0. If a 0.0.6 patch is published that the peer range accepts, it won't be tested locally during development.

Suggested change

	"@antelopejs/interface-core": "^0.0.5",
	"@antelopejs/interface-core": ">=0.0.5 <0.1.0",

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 40

Comment:
The `^0.0.5` specifier in devDependencies does not mirror the peer range. For `0.0.x` versions, npm/pnpm treats the caret as a patch-level pin (`>=0.0.5 <0.0.6`), meaning the dev install is locked to exactly `0.0.5` while the peer range allows any `0.0.x` up to `0.1.0`. If a `0.0.6` patch is published that the peer range accepts, it won't be tested locally during development.

```suggestion
    "@antelopejs/interface-core": ">=0.0.5 <0.1.0",
```

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

[Upd4ting]

@greptileai review