Updating Node and NPM

  • Hi,

    I have actually given up on the forum for the time being due to lack of interest. I am thinking of just doing a test forum just for me only and to practice etc but that will be sometime in the next months.

    In the meantime I have a question that I feel here is the best place to ask 🙂 Love the forum the look and the great advice.

    I am basically running just 1 app on my home server for gaming that uses node.js and npm. Both my versions of those are older versions but I know sometimes in the past after an update it ‘broke’ the app making me now reluctant to update again. Why change a winning side right? It works.

    What is the correct way to update them both. Clear cache needed etc? I will do a back up before (if) I update the versions.

    Hope all are ok and safe. Thanks for any replies.


  • @Sampo2910 before we start, do you know if the app itself you are running is compatible with the latest release of NodeJS ? I don’t expect npm to be an issue as it’s the Node Package Manager.

  • @phenomlab Hi thx for the reply.

    I am using this https://github.com/byNeHo/CoD4x-WebAdmin

    NeHo does not update it so much to be honest. I spoke to him and he does it from ‘time to time’

    I installed nvm so I can see the latest version of node etc and I guess i can just roll back if it does not work?

    Is there a way I can see what the app version of Node is? Then i could install ‘up to that’ and keep an eye out for any changes?

    As i said I am also all for not breaking a winning side haha and leave it as it is.

  • @Sampo2910 I think the best approach is to perhaps install this in a virtual machine where you can setup everything new, then attempt to install the app itself to ensure it works as desired before you attempt the actual upgrade on your server.

    The virtual machine itself can be installed on your own PC and will act just like an independent machine but of course is part of your own machine.

    Are you familiar with virtual machine concerts? Happy to help with this if needed.

  • @Sampo2910 said in Updating Node and NPM:

    Is there a way I can see what the app version of Node is? Then i could install ‘up to that’ and keep an eye out for any changes?

    Have a look in the source code for the app you are using, or better still, look at the GitHub page which should give you an idea of the version number which is the latest.

    In the source code you have running, there is typically a README file which should state the version you are running.

  • 4 Votes
    9 Posts

    @Hari Interested to know how you got on with the GHOST journey 🙂

  • Embeds

    4 Votes
    4 Posts

    @OT Are you testing embeds, or did you insert this link for another purpose? For clarity, this isn’t a testing category 🙂

  • Nodebb design

    Solved General
    1 Votes
    2 Posts

    @Panda said in Nodebb design:

    One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum.

    From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over.

    @Panda said in Nodebb design:

    The “write api” is preferred for server-to-server interactions.

    This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write.

    A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase.

    You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.

  • 1 Votes
    4 Posts

    @Vijay-Kumavat-0 I think you’d be better off customising the plugin above to be honest. It seems like you’d be reinventing the wheel otherwise.

    I’d modify


    These seem to be the two files that control what is in the dropdown lists.

  • 2 Votes
    6 Posts

    @dave1904 I’d start by adding a console.log function to hookData so you can see what is being returned

    return hookData; console.log(hookData):
  • 2 Votes
    2 Posts

    @Panda I have the same opinion here. NextJS is a framework for react, and like angular, I was never one to simply dive off into the deep without having any real need to do so. I’m conversant with nodeJS, vanilla js, and several other languages (including PHP which I have years of experience in and developed / still maintain an application at work that was custom written by me to fulfill an audit requirement), and in all honesty, I don’t really want to spend my life learning new frameworks unless I have a need to do so.

    I’ve been on the nodeJS train for some time now, and given my adoption of NodeBB, this makes perfect sense.

    Bleeding edge is fun if you want to experiment and learn, but with so many frameworks popping up all over the place, how many do we actually need?

    I guess most of this really depends on unique use cases, but I’ve yet to come across an issue that meant I had to rewrite an application in a different language to resolve an issue. It’s almost like using a bulldozer to find a china cup.

  • node vs nodejs confusion?

    Solved Configure
    1 Votes
    2 Posts

    @eeeee have a look at the below


    curl -sL https://deb.nodesource.com/setup_lts.x | sudo -E bash - sudo apt-get install -y nodejs

    You’ll notice that we are in fact “installing” NodeJS but never actually have a need to reference it. Here’s the nodejs --version command on my dev system


    More detail here