Closed ghost closed 3 years ago
If you want some additional granularity on when it worked last: my package version pushed on 8 April is showing up but not my version pushed 9 April.
Newly uploaded packages not showing up. Don't know why.
jsoning
is a public package. But on npms.io
API it says not found.
Same issue here!
I published a package (git-assist
) a few minutes ago as well as multiple other times this week. The latest version should be 1.1.0
but the search shows the version as being 0.6.12
and published over a week ago.
Having the same issue with my package. Pushing major updates and its been 48hrs+ and still not seeing anything. What's the expected lag time for updates to be reflected?
The package I'm trying to update: npmm
Having the same issue here. Does the server treat updates differently than new packages? I didn't have an issue when I made a new package, just when I updated.
Same problem for @types/react-select
:
https://npms.io/search?q=%40types%2Freact-select
shows 1.2.6, should be 3.0.22
Same issue with mws
package.
I got the name from the original author and published a new version. It's been over a month and the old meta data is still shown in search results.
I've published multiple new versions of rjsf
, including publishing a documentation website, but the last update according to npms.io was 2020-09-24
The analyzer had some issues and wasn't running for a few days. It's now slowly catching up. As an example, rjsf
is now updated.
Will close this, feel free to comment if you see further issues.
mws package is still not updated
https://npms.io/search?q=%40types%2Freact-select
still shows 1.2.6, should be 3.0.26
New package isn't showing up, @replygirl/tc
first version published 19 days ago
I first noticed that the version of my package is deprecated: node-red-contrib-time-switch
After having a closer look it seems to affect all packages updated within the last days. e.g: react-vapor
Everything updated around two month ago is properly there.