anomalyco / anomalyco/opencode
bun install fails intermittently in CI/CD: @solidjs/start pinned to flaky pkg.pr.new registry (404)
@neriousy is already working on this.
Since Sep 1, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
bun install intermittently fails with 404 Not Found when resolving @solidjs/start, which is pinned to https://pkg.pr.new/@solidjs/start@dfb2020 in the root package.json catalog. This breaks containerized CI/CD builds that run bun install against the opencode monorepo.
pkg.pr.new is StackBlitz's on-demand PR-preview npm registry. It intermittently 404s due to rate-limiting and cold-start behavior (it builds packages from GitHub PR commits on demand). The 404s are transient — the URL may return 200 minutes later — but they reliably break CI pipelines that can't tolerate flaky dependency resolution.
The pkg.pr.new artifact comes from solidjs/solid-start PR #2015 ("temporary clone all responses"), whose author explicitly wrote:
"ignore this PR i need to do this to test something with pkg pr"
This is a throwaway test PR, not a meaningful feature PR. The latest published @solidjs/start on npm is 2.0.4 and is the correct source.
This was previously raised in #27422 but was auto-closed as a "question" by the issue triage bot. Filing as a bug per CONTRIBUTING.md guidelines.
Plugins
N/A — build/dependency issue, not plugin-related.
OpenCode version
v1.18.18 through v1.18.25 + dev branch HEAD (all still pin the pkg.pr.new URL at package.json:89).
Steps to reproduce
- Clone opencode at any tag from v1.18.18 onward (or
devHEAD) - Run
bun installin a CI/CD container or any environment where pkg.pr.new rate-limits or cold-starts - Observe:
error: failed to download @solidjs/start@https://pkg.pr.new/@solidjs/start@dfb2020: 404 Not Found bun installexits 1; build fails
The failure is intermittent — re-running may succeed (the URL returns 200 when pkg.pr.new is not rate-limiting). But it fails frequently enough to block CI pipelines (observed twice in a single day in our production CI).
Screenshot and/or share link
Error output from CI:
error: failed to download @solidjs/start@https://pkg.pr.new/@solidjs/start@dfb2020: 404 Not Found
Operating System
Linux (Docker, debian:bookworm-slim builder stage)
Terminal
CI/CD (GitHub Actions, self-hosted runners)
Proposed fix
Switch the catalog entry from the pkg.pr.new URL to the published npm version:
- "@solidjs/start": "https://pkg.pr.new/@solidjs/start@dfb2020",
+ "@solidjs/start": "2.0.4",
A fix PR is available at: https://github.com/anomalyco/opencode/compare/dev...padraig-myers-sh:opencode:fix/solidjs-start-published-version
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.