Skip to content
Sudonix

build nodebb Warning in entrypoint size limit

Solved Performance
2 2 1.0k 1
  • Pandaundefined

    I saw in the output from ./nodebb build , 2WARNING s:
    Firstly)

    **Entrypoint ... combined size exceeds recommended limit (244 KiB)
Entrypoints:
-nodebb (355 KiB)
-admin (294 KiB)

    what does this mean, and is it a problem?

    Secondly)

    WARNING in asset size limit (and listed 4 min.js files)
    0
  • Pandaundefined Panda

    I saw in the output from ./nodebb build , 2WARNING s:
    Firstly)

    **Entrypoint ... combined size exceeds recommended limit (244 KiB)
Entrypoints:
-nodebb (355 KiB)
-admin (294 KiB)

    what does this mean, and is it a problem?

    Secondly)

    WARNING in asset size limit (and listed 4 min.js files)
    phenomlabundefined

    @eeeee they are nothing to worry about, and can be ignored.

    Mark Cutting also advises organisations as a Fractional CIO, Fractional CISO and Executive Advisor, helping boards improve technology governance, cyber resilience and executive decision making. Learn more at Phenomlab Ltd

    0
  • phenomlabundefined phenomlab has marked this topic as solved on
Log in to reply

Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • DownPWundefined

    Tutorial : NodeBB Scaling-clustering Redis + Proxied Cloudflare Free plan : integration guide

    Performance nodebb scaling redis cloudflare socket.io
    3
    4 Votes
    3 Posts
    1k Views
    crazycellsundefined
    thanks @DownPW ! this is definitely very helpful.
  • cagatayundefined

    What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    4k Views
    phenomlabundefined
    @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. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 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. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list 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 - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 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.
  • Pandaundefined

    Sidebar Widget is no longer on the side!

    Moved Solved General nodebb
    4
    2
    2 Votes
    4 Posts
    1k Views
    phenomlabundefined
    @Panda said in Sidebar Widget is no longer on the side!: Ah, so sidebar wont work on mobile? Correct. If you review the docs on bootstrap, you’ll notice that it is designed on a grid system https://getbootstrap.com/docs/5.0/layout/grid/ What I mean by changing the category is moving it on here to general as you posted it in bugs, when it isn’t.
  • Pandaundefined

    Removing blue 'moved' tag from post

    Solved Configure nodebb
    16
    2
    3 Votes
    16 Posts
    5k Views
    Pandaundefined
    @phenomlab Ah, got it working! I reversed the CSS addition to put z index high, and then I could see another error box saying fork title must be at least 3 characters. So made the new fork title longer and button responded.
  • cagatayundefined

    NodeBB v3 Chat Very Slow

    Moved Performance nodebb v3 nodebb chat
    47
    11 Votes
    47 Posts
    18k Views
    phenomlabundefined
    @DownPW Seems fine.
  • phenomlabundefined

    Optimum config for NodeBB under NGINX

    Performance nginx performance
    4
    3 Votes
    4 Posts
    2k Views
    phenomlabundefined
    @crazycells hi - no security reason, or anything specific in this case. However, the nginx.conf I posted was from my Dev environment which uses this port as a way of not interfering with production. And yes, I use clustering on this site with three instances.
  • phenomlabundefined

    NodeBB slow after DB recovery

    Solved Performance performance nodebb
    1
    5 Votes
    1 Posts
    828 Views
    No one has replied
  • RiekMediaundefined

    nodebb-plugin-customize error

    Solved Customisation
    25
    2 Votes
    25 Posts
    14k Views
    RiekMediaundefined
    @phenomlab it work, thanks