-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Web UI not listing packages because of 'time' property unavailability in package.json in storage dir #758
Comments
fix: normalize package was broken #758
Please try with |
Verified, thank you! @juanpicado One related minor UI (alignment) issue in the home page I noticed when there are packages with/without the |
@kumarvi I don't get it. License is missing? |
The license div is not right aligned, for the older packages, because of the missing time info div on the left side. |
Ohh !! I must be blind. I'll create a ticket. Thanks 👍 |
@kumarvi @juanpicado I am creating a separate issue for this. 🥇 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Describe the bug
We're trying to migrate from sinopia to verdaccio for our internal npm registry, and noticed that the internal packages that were published using our existing setup (using sinopia) aren't showing up in the Web UI with the latest verdaccio (version: 3.1.2), even though we're able to install them. This is happening because of the some of the packages that were published earlier seem to be missing the
time
property in the package.jsonTo Reproduce
Ensure a module is already published once to verdaccio. Remove the
time
member from the package.json inside the storage directory. Then try to load the Web UI home page.Results:
verdaccio.log
during server start-upAdditional context
There has to be a
isNil
check for thetime
property in https://github.com/verdaccio/verdaccio/blob/master/src/lib/storage.js#L374, similar to the fix done in e977d50 to support backward compatibility.The text was updated successfully, but these errors were encountered: