• 4 Votes
    1 Posts

    We will be dropping support for nodejs 14.x in nodebb 3.x.

    Nodejs 14 will be out of maintenance in april 2023 and some of our dependencies no longer support it.

    You can see nodejs release schedule here https://github.com/nodejs/release#release-schedule

  • 0 Votes
    4 Posts

    No, in the previous update, a redis package was replaced via ioredis package. And that change is broke your configuration.
    Related PR: https://github.com/NodeBB/NodeBB/pull/9545

  • 0 Votes
    2 Posts

    This isn't a forum for node.js help. It's the community forum for NodeBB, a node.js based forum software.

  • 0 Votes
    11 Posts

    Always best to, just in case πŸ˜ƒ I believe socket.io will need to rebuild its binaries.

  • 0 Votes
    6 Posts

    @Bri Yes there are solutions like Microsoft's vcpkg or even cppan.

    But my tool would be more like a deployment complement: you would generate your binaries for the end user to download them but also an amalgamated version in case they want to use the quick n easy way.

    One thing I'd like to setup if this happens to be successful would be a cloud service which would allow to easily amalgamate your project.

  • 1 Votes
    13 Posts

    Just using function syntactic sugar var hello = (name) => {....} πŸ˜„

    And this makes code clear in async flow

    async.waterfall([ (next) => { next(err, 'name') }, (name, next) => { next(err, 'final') } ], callback)
  • Learn Nodejs

    NodeBB Development
    1 Votes
    5 Posts

    Just practice -- just build things. I have my coisin-in-law (is that a real term?) learning Node.js via Tessel, even though:

    It's kind of expensive They don't use NodeBB to power their forums πŸ˜†

    Try nodeschool. If you respond well to it, then keep using it. The key is to find programming fun and gain that sense of accomplishment.

  • 0 Votes
    5 Posts

    You know (one of) the main difference(s) between TCP and UDP, don't you?

    TCP is connection-oriented, UDP isn't. So there is no UDP core-functionality to check whether the receiver is alive (/has the port opened).

    You'd either need to create server-side code or know the server-behavior (e.g. responses to specific datagrams) to achieve an UDP port-scanner.

    If you're able to write server-side code the best is to ask for UDP port status via TCP since it has reliable data-transfer implemented.

  • 0 Votes
    1 Posts

    Well, I have this issue that I need to do following things:
    1.Mongo Find
    2. Foreach
    3. MongoFind
    4 one more Foreach.

    because of asynchronaus mongo calls it is difficult to get proper result, however process.nextTick should handle this problem and still I have problem:

    function find(dbComm) {

    dbComm.forEach(function (current) { id= parseFloat(current.ID); db.anotherCollection.find({ ID: id}, function (error, result) { result.forEach(function (rank) { if (parseFloat(result.ID) == parseFloat(current.ID)) { rank.rank = 'Some calculations'; } }); }); });


    app.get('/someparams', function (req, res) {

    db.collection.find().sort({ "rank": order }).skip(pagenumber).limit(5, function (err, result) { process.nextTick(function () { find(result, function () { }) }); process.nextTick(function () { res.send(result); }); });

    And on client side I should recive an array where the rank equals 'Some Calculations'
    but unfortunetly it is not...
    However...! If I add setTimeout(function(){}) before res.send(result) (and res.send(result) will be placed inside setTimeout) it actually does work and on client side I recive data with "Some Calculations" but it is just timeout and it fails sometimes and client dont recive "Some Calculations"
    if I put process.nextTick instead of setTimeout it doesnt work and "Some calc..." are not sent.

    Something is beeing done eralier then it should (probably in forEach in find() function)
    and my question is how to deal with it? maybe I should put process.nextTick in different function ?

  • 0 Votes
    4 Posts

    test tst test

  • 1 Votes
    1 Posts

    The current steps outline how to compile the package yourself, however, they do now have a version for the raspberry pi, well, up to 0.10.26 anyway.

    So might be worth changing the Debian NodeJS section with

    wget http://nodejs.org/dist/v0.10.26/node-v0.10.26-linux-arm-pi.tar.gz tar -xvzf node-v0.10.26-linux-arm-pi.tar.gz node-v0.10.26-linux-arm-pi/bin/node --version

    You should see: v0.10.26

    NODE_JS_HOME=/home/pi/node-v0.10.26-linux-arm-pi PATH=$PATH:$NODE_JS_HOME/bin npm β€”version

    You should see: 1.4.3

    Not sure if this helps or not.. πŸ˜†