The CLI update notifier currently determines whether a newer Aspire CLI exists from the existing CLI package metadata, then chooses package-manager-specific guidance based on local install detection. For npm-installed CLIs, that can produce a confusing experience if the NuGet/app metadata has moved ahead but the npm pointer package is not live yet, is still propagating, or npm publishing was skipped/delayed: the CLI says an update is available and suggests npm install -g @microsoft/aspire-cli@latest, but npm may report that there are no updates or reinstall the same version.
We should revisit this for npm installs so the update guidance lines up with what npm can actually serve. Possible directions:
- use npm registry metadata as the update source when the CLI is running from the npm launcher
- suppress the npm-specific update hint until the npm pointer package is at-or-above the suggested version
- keep the current NuGet-based version decision but add a low-cost/cached npm availability check outside the hot notifier path
Tracked from #17766 (comment).
The CLI update notifier currently determines whether a newer Aspire CLI exists from the existing CLI package metadata, then chooses package-manager-specific guidance based on local install detection. For npm-installed CLIs, that can produce a confusing experience if the NuGet/app metadata has moved ahead but the npm pointer package is not live yet, is still propagating, or npm publishing was skipped/delayed: the CLI says an update is available and suggests
npm install -g @microsoft/aspire-cli@latest, but npm may report that there are no updates or reinstall the same version.We should revisit this for npm installs so the update guidance lines up with what npm can actually serve. Possible directions:
Tracked from #17766 (comment).