license-report icon indicating copy to clipboard operation
license-report copied to clipboard

Release date of the installed version

Open benispeti opened this issue 1 year ago • 8 comments

Is it possible to add a "Build in" field support for the date of the installed version? (I can see that the date of the remote version is already supported, but that's not what I'm looking for)

benispeti avatar Sep 12 '24 13:09 benispeti

which field in the package.json or the npmjs package data contains the date of the installed version (whatever that might be)?

BePo65 avatar Sep 12 '24 16:09 BePo65

As far as I see this information is not available from package.json. I found the following way to gather the date of a particular npm package, not sure if this helps. npm view rxjs time[6.6.6]

benispeti avatar Sep 12 '24 18:09 benispeti

This won't be easy. By now we can only define fields from the package.json in our config file.

What do you use the date for? To check when the package was updated?

BePo65 avatar Sep 13 '24 17:09 BePo65

As you probably know we have a field latestRemoteModified that contains the date for the latest version on the server. Will this be enough?

BePo65 avatar Sep 14 '24 05:09 BePo65

Yes, I saw the latestRemoteModified field, that was not what I was looking for. Btw how the latest remote version and modified date is queried?

benispeti avatar Sep 17 '24 13:09 benispeti

The latestRemoteModified is set in the addPackageDataFromRepository.js file (here named lastModified).

As you know, we get the 'remote' data from the registry (e.g. for semver.

For me it remains the question, what you will use these dates for? To get a feeling, how old the version is compared to the latest available?

BePo65 avatar Sep 17 '24 17:09 BePo65

I checked the semver example and I think the date information is available for each release version too, not only the lastModified date. Copying a snippet here:

"time": {
    "created": "2011-02-12T00:20:25.690Z",
    "modified": "2024-07-31T15:24:46.517Z",
    "1.0.0": "2011-02-12T00:20:26.037Z",
    "1.0.1": "2011-02-18T17:15:49.775Z",
    "1.0.2": "2011-03-22T21:27:35.218Z",
    ...

Based on the registry response I think the release date of a given version could be identified.

benispeti avatar Sep 23 '24 10:09 benispeti

i know that the date is available, but the question is: "what do you need this date for" and "why should it be added to the tool" (i.e. is it a use case "many" other could have too?).

So would you be so kind, to tell me a little bit more about your use case?

BePo65 avatar Sep 24 '24 04:09 BePo65

closed issue because of inactivity for 5 months

BePo65 avatar Mar 01 '25 09:03 BePo65