[GH-ISSUE #689] solid-js peer dependency should use version range instead of exact version #953

New issue

Open

opened 2026-03-14 09:08:32 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 09:08:32 +03:00

Owner

Originally created by @konard on GitHub (Feb 15, 2026).
Original GitHub issue: https://github.com/anomalyco/opentui/issues/689

Originally assigned to: @Adictya on GitHub.

Description

The @opentui/solid package specifies an exact version for the solid-js peer dependency, which causes warnings when installing packages that depend on @opentui/solid with a different (but compatible) solid-js version.

Current Behavior

@opentui/solid@0.1.79 specifies:

{
  "peerDependencies": {
    "solid-js": "1.9.9"
  }
}

When a package depends on solid-js@^1.9.10 (which resolves to 1.9.11), Bun shows:

warn: incorrect peer dependency "solid-js@1.9.11"

Expected Behavior

The peer dependency should use a semver range like ^1.9.9 to accept any compatible version:

{
  "peerDependencies": {
    "solid-js": "^1.9.9"
  }
}

Reproduction

mkdir test-opentui && cd test-opentui
bun init -y
bun add solid-js@^1.9.10 @opentui/solid@0.1.79

Output:

warn: incorrect peer dependency "solid-js@1.9.11"

Environment

@opentui/solid: 0.1.79
solid-js: 1.9.11
Bun: 1.3.8

Context

This issue was discovered while working on link-assistant/agent#186.

Suggested Fix

Change the peerDependencies in @opentui/solid package.json from:

-  "solid-js": "1.9.9"
+  "solid-js": "^1.9.9"

This would allow any patch version of solid-js 1.9.x to be used, which is the standard practice for peer dependencies.

Originally created by @konard on GitHub (Feb 15, 2026). Original GitHub issue: https://github.com/anomalyco/opentui/issues/689 Originally assigned to: @Adictya on GitHub. ## Description The `@opentui/solid` package specifies an exact version for the `solid-js` peer dependency, which causes warnings when installing packages that depend on `@opentui/solid` with a different (but compatible) solid-js version. ## Current Behavior `@opentui/solid@0.1.79` specifies: ```json { "peerDependencies": { "solid-js": "1.9.9" } } ``` When a package depends on `solid-js@^1.9.10` (which resolves to `1.9.11`), Bun shows: ``` warn: incorrect peer dependency "solid-js@1.9.11" ``` ## Expected Behavior The peer dependency should use a semver range like `^1.9.9` to accept any compatible version: ```json { "peerDependencies": { "solid-js": "^1.9.9" } } ``` ## Reproduction ```bash mkdir test-opentui && cd test-opentui bun init -y bun add solid-js@^1.9.10 @opentui/solid@0.1.79 ``` Output: ``` warn: incorrect peer dependency "solid-js@1.9.11" ``` ## Environment - @opentui/solid: 0.1.79 - solid-js: 1.9.11 - Bun: 1.3.8 ## Context This issue was discovered while working on [link-assistant/agent#186](https://github.com/link-assistant/agent/issues/186). ## Suggested Fix Change the `peerDependencies` in `@opentui/solid` package.json from: ```diff - "solid-js": "1.9.9" + "solid-js": "^1.9.9" ``` This would allow any patch version of solid-js 1.9.x to be used, which is the standard practice for peer dependencies.