Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Latest version doesn't mach remote version

See original GitHub issue

Hallo.

I found that the output returns always the same versions:

These two props return the correct values:

json['dist-tags']['latest']
json['dist-tags']['next']

example:

packageEntry.version 7.2.12
localVersionSemverRange 7.2.12

version 7.2.12

latest version 14.1.0
next version 14.1.0-rc.0

but script return:

{
  name: '@angular/core',
  author: 'angular',
  licenseType: 'MIT',
  link: 'git+https://github.com/angular/angular.git',
  definedVersion: '7.2.12',
  installedVersion: '7.2.12',
  remoteVersion: '7.2.12',
  comment: '7.2.12'
}

Issue Analytics

State:
Created a year ago
Comments:5

Top GitHub Comments

2reactions

BePo65commented, Jul 25, 2022

What version information do you need? Most (all?) npm packages have a latest dist-tag (or at least it should be possible to find out, what is the highest number), but not all packages do have a next tag.

So I could agree that we should add a latest version field, probably as optional field, to keep backward compatibility. This would not give you the latest compatible version (as there is no range pattern, but at least the latest available version.

How about that?

0reactions

BePo65commented, Jul 31, 2022

Solved by pr #105