Could not determine version for package... #16162
Labels
freq1: low
Only reported by a handful of users who observe it rarely
severity5: regression
type: bug/fix
Milestone
🐞 Bug report
Command (mark with an
x
)Description
The
A clear and concise description of the problem...ng update
command fails when a package uses thegit+ssh://
orhttps
reference rather than a version number (as you usually have). While this is definitely not best practice, it happens from now and then inside enterprise environments.🔬 Minimal Reproduction
Add a package referenced via
git+ssh
, for instance:"@biesbjerg/ngx-translate-extract": "git+ssh://git@bitbucket.org:r3_gis_dev/ngx-translate-extract.git#3.0.5-r3patch.01",
Having this in the
package.json
runng update @angular/core@next @angular/cli@next
.As a concrete example of an external package, this one should also fail:
🔥 Exception or Error
🌍 Your Environment
//cc @filipesilva
The text was updated successfully, but these errors were encountered: