Posts

• ---

  What’s going on with NodeBB?
  undefined phenomlab

  @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it.

  Method 1: Using NVM (Recommended)

  If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed.

  1. Install Node 22:
     nvm install 22
  2. Switch to Node 22:
     nvm use 22
  3. Set it as your default:
     nvm alias default 22
  4. Verify the change:
     node -v

  ---

  Method 2: Using NodeSource (PPA)

  If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version.

  1. Remove the old NodeSource list (optional but cleaner):
     sudo rm /etc/apt/sources.list.d/nodesource.list
  2. Download and run the NodeSource setup script for Node 22:
     curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash -
  3. Install/Upgrade Node.js:
     sudo apt-get install -y nodejs
  4. Verify the installation:
     node -v

  ---

  Method 3: Using the ‘n’ Package

  If you have npm installed, you can use the n interactive manager.

  1. Clear the npm cache:
     sudo npm cache clean -f
  2. Install the ‘n’ helper:
     sudo npm install -g n
  3. Install Node 22:
     sudo n 22
  4. Update your shell:
     hash -r

  Troubleshooting

  • Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo.
  • Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc.
  • Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined cagatay

  how to upgrade nodejs v20 to v22?

  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined cagatay

  I don’t want to keep worrying about whether the script will break with every update. Yes, we invested a lot of effort, yes, I have custom code, and yes, everything works well but somehow I end up facing issues after every update. And honestly, I think they have a development approach that doesn’t really listen to users. They just add or remove things based on their own ideas. The social plugins were a complete disaster

  Performance nodebb script die

• ---

  [NodeBB] Focus Mode : simply immersive reading for NodeBB
  undefined DownPW

  Hey everyone,

  I’m not sure where to post this, I’ll let @phenomlab edit it if necessary.

  Already posted here : https://community.nodebb.org/topic/19318/focus-mode-simply-immersive-reading-for-nodebb

  I’ve been working on a small client-side script that adds an simply immersive reading mode to NodeBB. No plugin required, just a few lines of custom JS and CSS dropped into the ACP.

  I’m just sharing this here for fun : https://github.com/DroidBV8/nodebb-focus-mode

  

  What it does

  Pressing F (or clicking the icon in the right sidebar) hides everything that isn’t the content you’re trying to read:

  • Both sidebars
  • Header / brand bar
  • Footer
  • Topic thumbnails and sidebar tools (reply, follow, timeline)

  The content area reflows to a centered 860px column, font size bumps up slightly, and a reading progress bar appears at the top of the page.

  To exit: press F again, Escape, or click the floating button that appears in the bottom-right corner.

  ---

  Details

  Activation effect : a subtle CRT glitch effect plays on toggle. Three CSS variables let you dial the intensity up or down without touching the keyframes:

  --fm-glitch-opacity: 1;   /* 0.5 = subtle | 2 = heavy */
  --fm-glitch-skew:    1deg;
  --fm-glitch-shift:   4px;
  

  Keyboard : F to toggle. Ctrl+F, Cmd+F and Alt+F are ignored so you don’t accidentally trigger it when searching the page.

  Scroll preservation : when toggling, the layout shifts because sidebars appear/disappear. The script measures the position of the nearest visible post before and after the layout change, then compensates with scrollBy so you stay exactly where you were.

  Topic-only : the button is greyed out on non-topic pages with a tooltip explaining why. Pressing F outside a topic shows a small toast instead of doing nothing silently.

  Mobile: disabled entirely under 768px. No button injected, no state restored.

  Theming : all colors reference Bootstrap CSS variables (--bs-body-bg, --bs-border-color, --bs-primary, etc.) so it adapts automatically to any NodeBB theme, light or dark.

  State : saved in localStorage, restored on next visit. Uses try/catch so it degrades gracefully in private browsing.

  ---

  Implementation notes

  The script is a self-contained IIFE, hooking into the standard NodeBB client-side events:

  $(window).on('action:ajaxify.end',   function () { focusMode(); });
  $(window).on('action:topic.loaded',  function () { focusMode(); });
  // etc.
  

  The glitch effect is pure CSS @keyframes , the JS only adds/removes classes. Layout compensation is synchronous (getBoundingClientRect → scrollBy) with no setTimeout on the scroll itself, which avoids triggering NodeBB’s scroll-based URL updater in a loop.

  ---

  Compatibility

  Tested on NodeBB 3.x with Bootstrap 5 themes. Should work on any setup using the standard sidebar components (nav.sidebar-left, nav.sidebar-right).

  Customisation focus mode nodebb javascript css

• ---

  What’s going on with NodeBB?
  undefined DownPW

  Honestly, I don’t regret the move at all on my side but I get that the experience can be very different depending on how comfortable you are with the technical side. XenForo is definitely more forgiving if you don’t want to deal with the server.

  One thing worth keeping in mind though: your install has some custom code on it, and need to know what it does or stay to stock nodebb witout modification

  What’s actually frustrating you the most right now? If it’s day-to-day admin stuff, there might be simpler fixes than rebuilding everything on XenForo.

  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined cagatay

  To be honest, I really regret moving to NodeBB. I should have stayed with XenForo.

  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined DownPW

  That’s exactly our approach on PW now. Learned it the hard way , upgraded too early once or twice and paid the price. Actually sitting two releases behind at the moment, not just one. Stability over bleeding edge, unless a vulnerability forces the hand. Solid policy.

  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined phenomlab

  @DownPW I tend to stay at least one release behind intentionally to ensure maturity before upgrading - unless there is a good reason to do so immediately - such as identified vulnerabilities

  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined DownPW

  @cagatay said:

  I downgraded the version, and now it is working. I think the issue is related to the version.

  Maybe yes, maybe no. it can be plugins compatibility, nodejs, npm etc.

  I don’t upgrade for now. I still waiting a little before upgrade.
  I’m on 4.10.3

  Performance nodebb script die

• ---

  What’s going on with NodeBB?
  undefined cagatay

  I downgraded the version, and now it is working. I think the issue is related to the version.

  Performance nodebb script die