Repository navigation
fix(install): revalidate npm metadata so updates get the new release - #439
Conversation
npm reuses cached package metadata, so running the installer shortly after a release (or to update) could resolve the dist-tag to the previous version. Right after 1.1.0-beta.6 was published, a fresh install still got 1.1.0-beta.5. --prefer-online revalidates the cache. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Update npm install commands install/install.ps1, install/install.sh |
Both installers add --prefer-online to their npm install command. The existing Node PATH setup and other install options remain unchanged. |
Priority:
Estimated code review effort: 1 (Trivial) | ~4 minutes
Change: Bug fix
Possibly related PRs
- Waishnav/devspace#436: Changes both installers’ version defaults and documents reruns as the update path.
- Waishnav/devspace#435: Runs both installers and reruns the Unix installer, then checks the installed version.
- Waishnav/devspace#434: Introduces the shell and PowerShell installers and their npm installation commands.
Merge Risk: 
dc192
-
The installers now request fresh package metadata while retaining cached-response fallback for network failures in the inspected npm version. No actionable merge-blocking issue was established.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title clearly and concisely describes the main change: installers revalidate npm metadata so updates resolve the new release. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks the npm trail,
Fresh metadata, no stale detail.
Two installers hop along,
With --prefer-online in their song.
The cached crumbs give way to spring.
Comment @coderabbitai help to get the list of available commands.
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Right after
1.1.0-beta.6was published, running the installer still installed1.1.0-beta.5. The registry already reported the newbetatag, butnpm installresolved it from package metadata cached locally before the publish. Since rerunning the installer is how users update, the same thing would make an update quietly reinstall the old version for a while after each release.Both installers now pass
--prefer-online, which makes npm revalidate cached metadata before resolving the dist-tag. Verified by installing through the installer with fresh metadata: it resolvedbetato1.1.0-beta.6,doctorreportednode:sqlite, and the agent daemon started.🤖 Generated with Claude Code
Summary by CodeRabbit