@subesh-s Have you tried using the login utilities route in the write API? It should send back a valid session cookie.
Outdated packages on the NodeBB Package Manager
Mikael Jenkler Swedes
Fuck the World right
My official stance on this development is that the good folks at npm have not made it easy to discover what routes are available to query.
The two routes that I do use were scraped from various bits and pieces of blogs, StackOverflow questions, and some diving through the npm repo itself. The very fact that I had to search so hard for it, and that npm doesn't publish any API documentation, suggests that it's for internal use and thus I really cannot hold them accountable for having removed the route completely.
It's a disappointment, but we'll see what happens over the next couple days.
As of August 20th @ 1500 EDT, nbbpm is back in business :shipit:
After asking around and getting absolutely zero results, I realised that there had to be a way replicants of npm kept themselves up to date.
Some further digging led me to the CouchDB guide for the Changes Feed. Seems to be stable and isn't likely to be removed without plenty of notice, so now we check that every hour.
If by now your plugin is still showing an outdated version on nbbpm, please send a
PUTto the package manager (as detailed in OP) to tell nbbpm to refresh your plugin.
My installation shows all of the new new upgrades to the packages, but when I update through the ACP, if I do a hard restart, I get the following:
24/8 22:10  - info: Initializing NodeBB v0.7.3 [outdated] nodebb-plugin-composer-default v1.0.11, requires 1.0.9 24/8 22:10  - warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them: 24/8 22:10  - warn: ./nodebb upgrade [cluster] Child Process (20442) has exited (code: 0, signal: null)
The installed version is higher than the one noted as out-of-date and forces me to roll back through ./nodebb upgrade before it will start again.
@glitch @lombisi Yes, this will happen because those specific dependencies (composer-default being one) are now defined with an exact version number, and not a range.
Your specific version of NodeBB requires v1.0.9 of composer-default, and any later versions might be incompatible (though it is unlikely).
However, you raise a good point, in that the suggested versions for bundled packages should always match what is defined in
package.json, and not what nbbpm recommends.