@frissdiegurke is correct, we've moved the list of plugin hooks to the wiki.
It needs a bit of standardisation, since new hook documentation was added rather haphazardly, but most (if not all) of the hooks should be there. If not, they can be added by anybody who wants to, by editing the wiki doc itself.
@gerald-in-korea You can actually own Webstorm. There is a perpetual fallback license: https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-a-perpetual-fallback-license-
But like the others said, Visual Studio Code and Visual Studio 20xx are not the same at all. I'm actually using Visual Studio Code as my general text editor in Linux. Would never do that with any of the Visual Studio 20xx
And yes, Microsoft is horrible at naming their products.
I correctly assumed (and this has been validated through actual plugin upgrades) that the latest hash in npm points to the most recently published version, and not the highest version.
That is, given your plugin nodebb-plugin-example
If v1.0.0 is compatible with v0.5.4
If v1.1.0 is compatible only with v0.6.0
The latter is published first
A user typing npm install nodebb-plugin-example will receive v1.0.0 of the plugin, irrespective of what NodeBB version he/she is running, even though v1.1.0 is technically newer
Now, special note: The NodeBB Package Manager doesn't do this. When the ACP calls nbbpm to request a suggested package, we query npm for the plugin data, and sort the versions before checking compatibility, so this issue is moot.