@1castro https://github.com/pichalite/nodebb-plugin-emailer-mailjet/pull/3
It is up to @pichalite now.
[nodebb-plugin-reactions] Reactions plugin for NodeBB
-
How to install for test ?
I have test
npm i @nodebb/nodebb-plugin-reactionsbut I have error :npm i @nodebb/nodebb-plugin-reactions npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: [email protected] npm ERR! Found: [email protected] npm ERR! node_modules/nodebb-plugin-emoji npm ERR! [email protected]"4.0.2" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer [email protected]"^3.5.0" from @nodebb/[email protected] npm ERR! node_modules/@nodebb/nodebb-plugin-reactions npm ERR! @nodebb/[email protected]"*" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/nodebb/.npm/eresolve-report.txt for a full report. -
-
Uninstalling scoped packages from ACP is broken https://github.com/NodeBB/NodeBB/issues/10582.
You can uninstall from the CLI with
npm uninstall @nodebb/nodebb-plugin-reactions -
@DownPW Were you able to find a fix for this? Just ran into this issue as well:
npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: [email protected] npm ERR! Found: [email protected] npm ERR! node_modules/nodebb-plugin-emoji npm ERR! [email protected]"4.0.2" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer [email protected]"^2.2.0" from [email protected] npm ERR! node_modules/nodebb-plugin-reactions npm ERR! [email protected]"*" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/nodebb/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/nodebb/.npm/_logs/2022-05-24T19_48_05_893Z-debug-0.log -
Please try with
@nodebb/[email protected] -
-
@DownPW what is your URL in config.json? It must exactly match the URL at which you access the site in your browser.
-
Hello, I am trying to install this plugin with no success. I am running a Cloudron instance of node BB, and I can access the terminal (which, if I'm not mistaken, takes me to the docker container in which the node BB instance is installed/running.
My understanding is that the node BB community version of this plugin is no longer maintained actively and should not be expected to work.
However, it seems that there is a new, more maintained version. Here's what I tried:
[email protected]:/app/code# npm i @nodebb/nodebb-plugin-reactions npm WARN reify Removing non-directory /app/code/node_modules npm ERR! code EROFS npm ERR! syscall unlink npm ERR! path /app/code/node_modules npm ERR! errno -30 npm ERR! rofs EROFS: read-only file system, unlink '/app/code/node_modules' npm ERR! rofs Often virtualized file systems, or other file systems npm ERR! rofs that don't support symlinks, give this error.I also tried
npm i @nodebb/[email protected], which gave the same output.Any help installing this would be greatly appreciated.
NodeBB 2.3.1
-
@prodigal_halogen Might be you need to reach out to the Cloudron team to ask what is happening.
It looks like it's trying to remove the
node_modules/folder, which is probably not what you want
-
I would like to implement notifications for this plugin. I have seen that @eshohet did a WIP implementation here: https://community.nodebb.org/topic/12332/new-features-for-nodebb-plugin-reactions. As that topic is nearly 5 years old and code has changed, did someone implement notifications for this plugin and using it today?
-
Anyone else noticed significant lag (and I'm talking 2 seconds for each click) as soon as you add a reaction to a post? Reloading the browser fixes the issue, but not great at all from the user experience.
Seems that my socket.io load has increased dramatically with this plugin, along with significant increase in CPU cycles. Based on this, I'm removing it, but leaving a note here to hopefully fix that as it's a useful plugin.
