[nodebb-plugin-color] Colors in posts
-
Seems like @toolito is indeed active though, that issue above was merged by him a few days ago
EDIT: Maybe he just forgot to publish to npm? Might be best to just bug him on his issue tracker
-
Yes @toolito is active on Github. But update to this one
https://github.com/Toolito/nodebb-plugin-colors/pull/6I've asked for npm ownership but I don't know if he did it or want to do it. And there's no way on npmjs to see if I'm owner.
-
The plugin in npm is outdated.
So, if you install it via
$ npm install nodebb-plugin-color
you get version at 27 July 2014 that doesn't work.If you clone the repo
$ cd /path/to/NodeBB/node_modules $ git clone https://github.com/Toolito/nodebb-plugin-colors
the plugin won't work until you rename folder
from
nodebb-plugin-colors
to
nodebb-plugin-color
But there is a way!
$ cd /path/to/NodeBB/node_modules $ npm i git+https://github.com/Toolito/nodebb-plugin-colors
After that the plugin finally works. (p.s. I didn't tested all claimed functionality, I just became convinced that
%(red)[Meow]
works)ping @toolito
-
Hello @Mega . Just curious, why does :
$ cd /path/to/NodeBB/node_modules
$ npm i git+https://github.com/Toolito/nodebb-plugin-colorsWork when nodebb-plugin-colors < with an "s" is at the end? I thought it supposedly worked without the "s"? Not doubting, just curious as to why it works that way for future reference.
Thank you for your help so far. I'm booting up Nodebb to test it out.
-
@JonDoe12 said:
Hello @Mega . Just curious, why does
Work when nodebb-plugin-colors < with an "s" is at the end?It's because of npm internal magic. It happens cuz package actually has proper name field in his
package.json
https://github.com/Toolito/nodebb-plugin-colors/blob/master/package.json#L2 -
@JonDoe12 Yup, it works with hex codes
-
Don't work on 0.6.1
-
Colors are disappearing if an enter made between lines?