That might be a nice workaround, although slightly nefarious in spirit
That said, I don't use Pushbullet anymore, as I no longer support them since they went pro. Happy to hand over the reigns to somebody else if a volunteer is available
Wouldn't it be nicer for plugin authors to always show 'compatible' with the last release that the plugin was compatible with?
I think I would be reluctant to add a badge to my READMEs that tells my potential users that this plugin doesn't (yet) work with a NodeBB version that has just been released.
Just a thought
We don't use any libraries that emulate classical inheritance. For namespacing we utilize:
For front end, we use require.js
The node.js backend uses (CommonJS module).
If you're writing a plugin, feel free to use whatever method you are comfortable with