Repository navigation
Conversation
|
Thanks for the pull request - the write-up made both changes easy to review. We've taken the repository-redirect part: the npm reverse lookup now resolves the canonical owner/repo through the GitHub redirect before giving up, so packages that moved keep resolving. It landed in 3762726 and will ship in the next release. The probe goes through curl so it honours the same proxy as the install and diagnostic channels. The preflight change is one we can't take. Since pnpm 10 blocks dependency build scripts by default, a package's prepare script does not run during these installs, so accepting a prepare-only source package would let preflight pass while the install still lacks its entry file. The supported channels stay: a complete npm package, committed build output, or a prebuilt release tarball (same call as #142). Closing this in favour of the redirect handling. Thanks again for the contribution. |
|
Thanks for taking the redirect fix. Understood about the preflight requirement; we'll use the complete npm package for Harmony. |
Follow GitHub repository redirects when resolving npm packages, and allow source packages with a
preparebuild to pass preflight. This fixes Harmony installation after its move to memorax-ai.Verified: typecheck, server/client builds, 9 existing resolver/preflight tests and live Harmony resolution; full suite: 116 passed, 2 skipped, 1 unrelated proxy probe failed.