-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: display release date #40
Labels
Comments
Good suggestion. Not sure yet how to implement to keep the output compact. I'm thinking of a new column with just the release age of the new version. |
To keep it concise, I've only the age of the new version. I don't think the old version age is really relevant.
|
silverwind
added a commit
that referenced
this issue
Mar 8, 2020
* update devDependencies (silverwind) * readme tweaks (silverwind) * remove travis badge (silverwind) * update json example, add TODO (silverwind) * readme tweak (silverwind) * add release age, fixes #40 (silverwind) * move jest to devDependencies (silverwind) * remove find-up dependency (silverwind) * tweaks (silverwind) * add node 13 (silverwind) * refactors (silverwind) * move requires to top (silverwind) * move test.json to file again (silverwind) * increase jest testTimeout (silverwind) * update dependencies (silverwind) * inline package.json in tests (silverwind) * update .gitignore (silverwind) * remove yarn.lock (silverwind) * remove travis (silverwind) * try actions (silverwind) * add yarn.lock to make travis install yarn (silverwind) * check if travis windows does include 'make' (silverwind) * use self to update (silverwind) * require node 10, rewrite tests to jest (silverwind) * Merge pull request #38 from fisker/fake-registry (silverwind) * chore: pin dependencies (fisker) * test: setup a fake registry (fisker) * use semver.validRange (silverwind)
Great, thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Registry response json has this info in
time
field on root.This better be human friendly format.
Maybe additionally time diff of those two dates.
Maybe like this
Problem: maybe too much info to display
Reason behind this request
The text was updated successfully, but these errors were encountered: