How long does it take a plugin published to npm to show up in nbbpm?

exodo

Last couple of weeks been forever till updates happen.
For my testing if it doesnt appear on 24h it wont appear so better do another update and wait the magic appears

deiden26

Bummer. I'll keep posting on occasion until it works. Thanks

exodo

@deiden26 said in How long does it take a plugin published to npm to show up in nbbpm?:

Bummer. I'll keep posting on occasion until it works. Thanks

I end up installingn manually cause i hate wait for 1 day
I have one update now 3 days and did yesterday another bump but still no pop

psychobunny

Nice widget btw

julian

Hm, odd.

It did work after I manually told nbbpm to update the plugin, so it shows up now: https://packages.nodebb.org/api/v1/suggest?package[]=nodebb-widget-search-bar&version=1.1.2

@deiden26 PUT, not POST

deiden26

@julian said in How long does it take a plugin published to npm to show up in nbbpm?:

Hm, odd.

It did work after I manually told nbbpm to update the plugin, so it shows up now: https://packages.nodebb.org/api/v1/suggest?package[]=nodebb-widget-search-bar&version=1.1.2

@deiden26 PUT, not POST

I actually was using PUT and not post, still had the following result for whatever reason

<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.10.0</center>
</body>
</html>

The original command was

curl -X PUT https://packages.nodebb.org/api/v1/plugins/nodebb-plugin-search-bar

EDIT: Now I see you are referencing my "I'll keep posting" comment. I just had my head in the forum lingo!

julian

Your plugin is nodebb-widget-search-bar, no?

deiden26

Hahaha. Yes, I might have mentioned it.

julian

@deiden26 Yes, in that case, your curl command is referencing the wrong package

deiden26

@julian Well, that explains a lot. I knew I was missing something very basic. One bad thing about pasting a command every time you want to run it instead of writing the thing out: the mistake you make once is the mistake you make EVERY TIME

Thanks for the sanity check!

julian

@deiden26 That said, you're not going insane, the package manager has been delayed in updating packages simply because npm resets their counter every once in awhile, and doesn't automatically notify nbbpm in any way. Will code a fix for it today so hopefully this is the last we'll hear of it.