Thank you 🙂
I update nodejs to 8.11.0 but it does not work. Which version of nodejs do we need? Here is the node version list: https://nodejs.org/en/download/releases/
fwiw; I use nodejs-12 on 1.12. Don't know about your emoji on 1.13.
Nodejs uses even numbers for production/stable releases and odd numbers for the bleeding edge. Some devs favor the latter. I favor the former and typically use the latest and greatest "stable" for all my nodejs stuff unless I have an explicit reason not to.
@sharonyue you need node 10 at least, I suggest that whenever you upgrade node, you upgrade to the latest lts (even number as he mentioned) version. In this case, that would be Node 12.
@torn2 said in Customize Emoji does not work:
You mean this one? I think its just alias. To some extend I think its not necessary to have both
aliases at the same time. I have many emojis and I found it is very difficult to name them. At last I end it by naming them by numbers
At first , I name them...
Finally , I just number them...since I cannot think an adequate name for these emojis..
Suggestions: can we make
Name not required?
Aliases are for additional names. For instance, you can add an alias for , allowing it to be accessed by
:happy: as well.
There needs to be some way of specifying an emoji do of course names are required. Try making them descriptively so they'll work well with autocomplete.
@sharonyue oh yes I do intend to look into that
@sharonyue needing to rebuild NodeBB for changes to apply is due to caching. Without rebuilding, NodeBB's cache-buster remains the same so even though the changes are there, you won't see them without clearing your cache.
There's also the problem of Windows where plugin assets are copied, not linked, so I'd have to start overwriting NodeBB's built assets instead of the ones in my plugin to get this to work.
In conclusion, for the forseeable future, the modifying emoji customizations flow will continue to be: